Thread: Setting up Server Runtime Manager v1.4 with your Server

Originally Posted by psyhoman

Nice thanks i will use that good job

Thanks, I enjoyed making it

Originally Posted by Riedell

Nice program! Started to use this and works out great! Thanks a lot!

+Rep

-Riedell

Thanks, i've worked hard on it

thanks m8, but does it restarts server if it crashes?

Originally Posted by kalamasnik

thanks m8, but does it restarts server if it crashes?

It depends on the type of crash, If its a NullPointer Exception or a OutOfMemory Exception then yes....

ok. well maybe you know how to fix this error? I was running server when it pop-uped this window about unhandled exception:


and here is details:

Code:

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

************** Exception Text **************
System.InvalidOperationException: Process has exited, so the requested information is not available.
   at System.Diagnostics.Process.EnsureState(State state)
   at System.Diagnostics.Process.get_WorkingSet64()
   at WindowsFormsApplication4.ServerManager.updateMem()
   at WindowsFormsApplication4.ServerManager.timeOut(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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Server Runtime Manager v1.4
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/Senukas/My%20Documents/Downloads/Server_Runtime_Manager_v1.4/Server%20Runtime%20Manager%20v1.4.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/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.42 (RTM.050727-4200)
    CodeBase: file:///C:/WIND/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

note server is still running. and it wont stop do this. thanks for help

Hmm, Could you give me a pic of your Settings...

And lets see...

at System.Diagnostics.Process.get_WorkingSet64()
at WindowsFormsApplication4.ServerManager.updateMem()
at WindowsFormsApplication4.ServerManager.timeOut(Obj ect sender, EventArgs e)


That is updating the Memory Usage.. (the bottom left) Hmm...

If what you say is true about the server still running, then the error should'nt happen...

I'm putting in a Try{}Catch{} right now in the code, so the next version should'nt have this error..... It will be released with 1.5