Back to Board Index
Back to Board Index
Forum help
| Framework error | |
Kenneth Brander   12th Apr 2014 14:07:19 | Hello Dave,
A rather interesting error has started to occur lately, it seems it started after one of the last updates. It seems to be related to the framework. When trying to close down the fso server module it appears a error message. One need to repeat trying to close it down and press "quit" on the error message for it to shut down. It will take everything from 4-5 tries to 20-25 but at this point one just gives up and do a ctrl alt delete and kill the process. This error is particularly bothering for us since we have a auto-restart system that restarts the server automatically each morning at 5:00 GMT. This to keep the server fresh and ready for the next day naturally as you may understand. We have in the past been told by you personally that we have left the server on to long at the time so this was our solution to that problem. The last four weeks I haven't been able to trust this function to work properly because of this error and there are some days I come in and the server is not restarted. This error obviously block the auto-restart but also on top of this it freeze the bot and session counter. The bot will not respond to any commands after the error occurs, it continue to spam its message further on the session list it will say zero users even if there are users in the session. ATCs will not show as active. Here is the error message that appears when it fails to shut down: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at am.a(Object A_0, FormClosingEventArgs A_1) at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e) at System.Windows.Forms.Form.WmClose(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.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.3625 (GDR.050727-3600) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- fsopenserver2 Assembly Version: 1.1.0.0 Win32 Version: 1.01.0.0 CodeBase: file:///C:/Program%20Files/FSopen%20Server/fsopenserver2.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3624 (GDR.050727-3600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3623 (GDR.050727-3600) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) 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.3082 (QFE.050727-3000) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3618 (GDR.050727-3600) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- PacketDotNet Assembly Version: 0.9.0.0 Win32 Version: 0.9.0.0 CodeBase: file:///C:/Program%20Files/FSopen%20Server/PacketDotNet.DLL ---------------------------------------- SharpPcap Assembly Version: 3.6.0.0 Win32 Version: 3.6.0.0 CodeBase: file:///C:/Program%20Files/FSopen%20Server/SharpPcap.DLL ---------------------------------------- ManagedWinapi Assembly Version: 0.3.0.0 Win32 Version: 0.3 CodeBase: file:///C:/Program%20Files/FSopen%20Server/ManagedWinapi.DLL ---------------------------------------- BeatlesBlog.SimConnect Assembly Version: 0.1.1.0 Win32 Version: 0.1.1.0 CodeBase: file:///C:/Program%20Files/FSopen%20Server/BeatlesBlog.SimConnect.DLL ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.1 built by: SP CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.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 framework is up to date so I really struggle to see what is wrong if any on our end of this and we would really appreciate if you could take a look at it since its a pain in the ass. We can naturally script in a solution in our auto-restart system but it would be much better if it could be solved with getting this at the root of the problem. If this is not something you can fix and a problem that are caused by the fso server module then please give us a heads up what needs to be done for this problem to be solved. I have tried sending you emails but have gotten no answer lately. Best Regards; Kenneth Brander kenneth@fsxeu.com http://www.fsxeu.com |
Dave Wave  13th Apr 2014 10:58:10 | It's just because I'm quitting fsopen without waiting for everything to finish cleanly. Pending database updates, listening to network traffic, simconnect, teamspeak etc.
I'll stick it on the list to do but, suspect it's going to take some time to resolve this one. |
| Tim Walters 13th Apr 2014 12:22:31 | My understanding is that this is a recent problem since one of the server updates. I might be wrong here though...
TimW FSXEU.COM |
| Dave Wave 13th Apr 2014 18:01:33 | I think your wrong as last update shouldn't have changed above. Are you doing anything different? |
| Kenneth Brander 13th Apr 2014 22:34:18 | Hey Dave,
I am not sure about it, but its seemingly one of the last updates. Maybe not the last update, may be wrong but still want you to look into this. We will probably go back to restarting manually now since we can't trust the system to restart automatically at all before this is fixed or at least identified. Best Regards; Kenneth Brander |
Chris Pringle   13th Apr 2014 23:41:26 | Hi Dave as said before I believe all these errors that everyone is having with logging in to flight strips is linked to the Microsoft net framework. I mean i have Microsoft net framework 4.5 now but before i had 3.5. When i had uninstalled flight strips and went back to re install it from the website, A message came up saying that Framework 3.5 is required. |
| Dave Wave 14th Apr 2014 00:00:07 | Chris:
1. This thread is about fsopen server not flight strips. 2. If no compatible .net framework is installed the software won't run. In this instance its running but generating an error on closing. |
You need to Log on to post a reply. |
Forum help