Unhandled Exception

[BG2518-Bob]

Hi Peter,

GREAT APP BTW - WILL BE DONATING

--------------------

Random crash ? - single time only - i.e. not repeated doing the same thing?

--------------------

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

An address incompatible with the request protocol was used.

--------------------

FYI the address and port used was an internal IP e.g. 192.168.1.192:51202

--------------------

Details copied FYI

--------------------

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException: An address incompatible with the requested protocol was used
at System.Net.Sockets.Socket.SendTo(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint remoteEP)
at System.Net.Sockets.UdpClient.Send(Byte[] dgram, Int32 bytes, IPEndPoint endPoint)
at JoinFS.LocalNode.DoGuaranteedMessages()
at JoinFS.LocalNode.DoWork()
at JoinFS.Network.DoWork()
at JoinFS.MainForm.DoWork(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
JoinFS
Assembly Version: 1.0.0.0
Win32 Version: 1.0.21.0
CodeBase: file:///C:/Program%20Files%20(x86)/JoinFS/JoinFS.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8750 (QFE.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.FlightSimulator.SimConnect
Assembly Version: 10.0.61259.0
Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.9268
Win32 Version: 8.00.50727.9268
CodeBase: file:///C:/WINDOWS/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e/msvcm80.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

---------------------------------------------------------------------------------------------------------------------------------------------------------

The option to continue produces looped UExcep. Only option was to Quit.

---------------------------------------------------------------------------------------------------------------------------------------------------------

Not sure this will in any way help - lol.

BG2518-Bob

[Peter]

Hi Bob,

thanks for letting me know about it. A bit tricky being a one-off crash, but it's useful to know about it.

Judging by the error message it looks like an issue with IPv6. Does that make sense, are your local network machines running IPv6?

JoinFS is intended to be purely IPv4, for a while anyway. I can certainly go through the code and ensure that it's correctly using the right protocol. That might help.

Thanks,
Peter

[BG2518-Bob]

Hi Peter,

Not using anything IPv6 here.

Plus, seen the exact same crash now on another completely separate stand alone PC that I was testing via TeamViewer after installing JoinFS.

On that PC (in Texas) we were trying to connect "Join" to the Pseudo Server I've set up here (UK) via my IP Address and port 4646.

Was getting a sort of hit and miss connection which I was trying to troubleshoot to no avail i.e. this connection seems flakey like it should be waiting a bit longer for a handshake or something. I have to say that when connection occurs it is blindingly fast but this guy has quite a slow connect speed so that may be triggering the error. NOTE I am having a wild guess at this but it sort of "feels right" - you know what I mean.

So perhaps some persistence at the attempt to connect is desirable?

You see I used the term Pseudo Server which really is a P3D installation on a PC doing absolutely nothing.

I'd like it very much if there was a dumb server version of JoinFS that has NO NEED for P3D or any other sim to be active.

And (more ideally) a version ala "JoinFS_Server" that could be running on a hosted server platform.

All with password protection of course.

I bet all of this is in your pipeline.

Cheers.

BG2518-Bob

[Peter]

Interesting what you said about the connection time. I was debugging the code yesterday and it appeared that if there was a slight delay in connecting then it failed to connect properly. Which is odd because the connection shouldn't be that time sensitive, but perhaps there is an issue there. Then again, that might be completely unrelated to what you are seeing.

You should be able to run JoinFS by itself without the simulator using the current version. The only requirement is that you have simconnect installed. I believe that there is an installer within the P3D installation. Might be under the redist folder or something like that. It's also available within the FSX:Steam installation under the SDK. I think it's the XPACK version that you need. If you install that on a server and run JoinFS it should work ok.

I'm not sure that you can run it without simconnect. Perhaps it would be possible to delink that as well. I'll have to look into that.

There is no password support at the moment, but yes, that will be in fairly soon. The way to run a private server at the moment is to just use a random 5 digit port number.

There will also be support for an ini file configuration so you can run JoinFS pre-configured and without the interface if you are running on a dedicated server. That should help.

Is your server running behind a router, and do you have port forwarding enabled? That may be causing the connection issues.

Peter

[BG2518-Bob]

Peter,

We had made exceptions through s/ware firewalls for all users as applicable plus we had made hardware router port forwarding rules also as applicable. So, 99.9% of connection issues are resolved. It was only AFTER doing all this that one user from Texas was experiencing intermittent connection problems to which I made my timeout suggestion. This is not stopping connection just occasionally failing to connect - that's @30-50% of attempts.

All that to one side for the moment please as we experienced last evening a problem whilst using JoinFS that I shall email you about rather than detail on here because it is rather sensitive.

BG2518-Bob

[Peter]

Hi Bob,

I think I managed to repeat this connection problem last night connecting to another server. It failed about 10% of the time. So perhaps there is a timing issue here. I'll investigate further. Fortunately it doesn't prevent one from connecting.

Peter

[marc2990]

I seem to have a similar problem.
I installed the program; I seem to be able to create my own session, but when I try to join a session I get this error message.
Details are as follows:
Zie het einde van dit bericht voor meer informatie over het aanroepen
van JIT-foutopsporing (Just In Time) in plaats van dit dialoogvenster.

************** Tekst van uitzondering **************
System.Net.Sockets.SocketException: Er is een adres gebruikt dat niet compatibel is met het aangevraagde protocol
bij System.Net.Sockets.Socket.SendTo(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint remoteEP)
bij System.Net.Sockets.UdpClient.Send(Byte[] dgram, Int32 bytes, IPEndPoint endPoint)
bij JoinFS.LocalNode.DoGuaranteedMessages()
bij JoinFS.LocalNode.DoWork()
bij JoinFS.Network.DoWork()
bij JoinFS.MainForm.DoWork(Object sender, EventArgs e)
bij System.Windows.Forms.Timer.OnTick(EventArgs e)
bij System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladen assembly's **************
mscorlib
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
JoinFS
Assembly-versie: 1.0.0.0
Win32-versie: 1.0.21.0
CodeBase: file:///C:/Program%20Files%20(x86)/JoinFS/JoinFS.exe
----------------------------------------
System.Windows.Forms
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5491 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.8686 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5495 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Windows.Forms.resources
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Configuration
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5494 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
mscorlib.resources
Assembly-versie: 2.0.0.0
Win32-versie: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.FlightSimulator.SimConnect
Assembly-versie: 10.0.61259.0
Win32-versie: 10.0.61637.0 (FSX-Xpack.20070926-1421)
CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll
----------------------------------------
msvcm80
Assembly-versie: 8.0.50727.6195
Win32-versie: 8.00.50727.6195
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/msvcm80.dll
----------------------------------------

************** JIT-foutopsporing **************
Als u JIT-foutopsporing wilt inschakelen, moet in het configuratiebestand voor deze
toepassing of computer (machine.config) de waarde
jitDebugging in het gedeelte system.windows.forms zijn ingesteld.
De toepassing moet ook zijn gecompileerd terwijl foutopsporing
was ingeschakeld.

Bijvoorbeeld:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wanneer JIT-foutopsporing is ingeschakeld, worden onverwerkte uitzonderingen
naar het JIT-foutopsporingsprogramma gestuurd dat op de computer is geregistreerd
en worden niet door dit dialoogvenster verwerkt.

I am not technically at all, so I have no idea what to look for; maybe you can help me? Attached a picture of the screen I get.
Cheers

[Peter]

Hi,

Are you specifying a port number in the join address or is it just in the format "0.0.0.0" ?

Did you enter the address in the Join box before clicking the Join button?

Peter