Unhandled exception

Suggestions, ideas and general discussion about JoinFS.
User avatar
Grumpy
Posts: 89
Joined: Mon Oct 10, 2016 2:30 am

Unhandled exception

Postby Grumpy » Sun Feb 26, 2017 11:33 pm

Peter, I keep getting this message box pop up.

Image


Contents are as follows

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: The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress
at System.Net.Sockets.Socket.ReceiveFrom(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint& remoteEP)
at System.Net.Sockets.UdpClient.Receive(IPEndPoint& remoteEP)
at JoinFS.LocalNode.ReceiveMessages()
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.5485 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
JoinFS
Assembly Version: 1.0.0.0
Win32 Version: 1.1.4.0
CodeBase: file:///C:/Program%20Files/JoinFS/JoinFS.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 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 Version: 2.0.0.0
Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
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.5495 (Win7SP1GDR.050727-5400)
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.5483 (Win7SP1GDR.050727-5400)
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.5494 (Win7SP1GDR.050727-5400)
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.6195
Win32 Version: 8.00.50727.6195
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a/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.


I have installed the latest ver .net Framework.
JFS 1.1.4 Stable

If I press Quit, the obvious happens
Press continue, it continues for several minutes, message returns.

On this puter, I usually have running...
FSX with the usual suspects of Saitek addons.
FSUIPC
IOBit malware checking
Teamspeak
a landing rate monitor

I am at a loss.
Replaced reinstalled JFS, Teamspeak, now tearing out what little remains of my hair.
GRRRRRR

User avatar
Peter
Site Admin
Posts: 1454
Joined: Fri Sep 23, 2016 8:51 am

Re: Unhandled exception

Postby Peter » Mon Feb 27, 2017 9:30 am

Hi Grumpy,

Interesting that I've not seen this before. Having done a bit of research on the error, it appears to be a temporary local problem related to your machine or possibly the network. Did you lose internet connectivity at the time?

It's basically more of a warning than a bad error, however, the reason it keeps showing the error like that is because there's a bit of missing code where I need to handle the problem specifically. This will be fixed in 1.1.7, which is very almost ready for release. ;)

Thanks for posting it.
Peter

User avatar
Chris_P
Posts: 16
Joined: Thu Dec 08, 2016 8:28 am

Re: Unhandled exception

Postby Chris_P » Mon Feb 27, 2017 4:55 pm

This will be fixed in 1.1.7, which is very almost ready for release.

That's great news ! 8-)

User avatar
Grumpy
Posts: 89
Joined: Mon Oct 10, 2016 2:30 am

Re: Unhandled exception

Postby Grumpy » Tue Feb 28, 2017 1:13 am

Peter wrote:Hi Grumpy,

Interesting that I've not seen this before. Having done a bit of research on the error, it appears to be a temporary local problem related to your machine or possibly the network. Did you lose internet connectivity at the time?


No, Peter, it occurs as soon as I invoke JFS. but it IS a new problem.

Peter wrote:It's basically more of a warning than a bad error,


Its no biggie, I just ignore it, makes no difference to operations.

Peter wrote:however, the reason it keeps showing the error like that is because there's a bit of missing code where I need to handle the problem specifically. This will be fixed in 1.1.7, which is very almost ready for release. ;)

Thanks for posting it.
Peter


No prob, you are building the best utility of its type, where we can help, we will.

B


Return to “Discussion”