Posted: Wed Oct 20, 2010 3:20 pm Post subject: ServerDoc doesnt close crash dialogs.
Hi
I am having some problem on my server. When a CSS server crashes, it shows a Assert Dialogue box which looks like this:
Can I somehow disabled this msg or can ServerDoc close this dialogue box and restart the server? If this dialogue box isn't closed the server cannot be restarted.
Hi Nomy,
Start your CCS, in serverdoc do a process dump. Now wait for crash. *WITH* that "Assert" window up do another process dump and email me sddump.txt file.
It shows on the windows login. I connect to my server using RDP. I wont be able to capture this error on sddump.txt because once I login, the error dialog disappears.
re the "application error" one try using VNC so the desktop is left open and not in a locked state. Maybe thats stopping the crash window appearing.
I have tried many VNC server/clients but I'm having to see a black screen after successful VNC login.
I have tried UltraVNC, RealVNC, TightVNC and TeamViewer and all of them have same result. They work fine after loging in from RDP but as soon as I disconnect from RDP. The desktop on VNC viewer hangs. Do you have a recommended VNC server application?
I think its to do with a security setting on Windows server 2003? I really don't know how to fix this.
Is it possible to run ServerDoc as a service and not as an application? So it works even if the desktop goes into a locked state and ServerDoc still kills the error dialog box?
The game servers are running on session 0 console.
I hope you can help.
EDIT:
I have tried to run serverdoc.exe as a windows service and I guess it doesnt work like that? or I'm doing something wrong.
Running as a service has the same issues - there is no desktop to display errors and some game servers fail to even work due to the missing interface.
Quote:
They work fine after loging in from RDP
Hmmm sounds like the computer is not booting into a desktop?? (auto login)
Ive seen UltraVNC working on Win7 so strange its not working on 2003. (though older UltraVNC was giving black screen)
The auto login is for when the Server is forced restarted. It logs in automatically on windows startup and runs the batch file start all.bat to start all serverdoc instances for srcds.
I have been using WinXP and it doesn't have this stupid login thing and the desktop remains active at all times even after closing(X) RDP client-side.
I have tried installing UltraVNC as a service and if I'm connected via RDP, I can use UltraVNC, but once I close RDP (I never logout), The VNC Viewer just stops responding as if the server doesn't responds anymore or has no screen? but srcds is working fine until of course when it crashes...
BTW, I think the Assert crash has been fixed, haven't seen it for a while so I guess it closes it
EDIT:
Ok, this is the end of my RDP era. I will not be using Remote Desktop Connection on Windows Server anymore because the way its working.
Once I logged in using RDP, UltraVNC just crashes or fails to log in. Works out great if you just stop using RDP.
I am now able to see the desktop screen on UltraVNC after a server restart. And I have set on UltraVNC to not to do anything after I disconnect from VNC so the desktop remains active. I hope this fixes the "Crash dialog box on login screen" issue on Windows Server 2003.
Thank You for this wonderful application and your help.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
