You are not logged in.
I'm making a new topic since the other was a mix-up .... my fault
I can't get my 1942 1.612 server to restart after a crash ... ?!
I run it in Win XP and have disabled error reporting.
I have enabled "Restart the server automatically" in "Options" in Battlefield Server Manager.
Any suggestions ?
Last edited by X=X=X=X=X=X=X=X (2012-11-24 18:41:04)
Are you sure the server doesn't restart?! It could be a server stall, the server gets stuck in a infinite loop. Check the CPU usage of BF1942_w32ded.exe, if it doesn't restart.
You can test if it restarts or not by closing the server, from the server console type "quit". I tested a BF1942 1.612 dedicated server under Windows XP and BFServerManager restarts the server.
I am 10000 % sure. It crashes roughly 1-2 times per 24 hours, and has done so the last seven days.
All the crashes feel and look exactly the same.
tuia, I haven't checked total system and BF1942_w32ded.exe CPU usage right after a crash, I will do that from now on.
Like said before, I run it under Win xp, directly on the desktop. Only non-Windows processes that run are BFRemoteManager.exe and BF1942_w32ded.exe.
I use these files :
http://team-simple.org/download/BF1942_ … layers.zip
http://team-simple.org/download/BFServe … atched.zip
I have screenshots of all the crashes. They all look identical, exept for variations in the "error numbers" :
( 0x00551619 0x00200079 <--------- these numbers )
Here's one of the screenshots :
Ok, what is probably stopping BFServerManager from restarting your BF1942 server is that pop-up dialog error message. Until you press OK or Cancel it won't restart. I think there is a program that can close those error dialogs automatically.
This may be the solution, haven't tested it yet :
http://support.microsoft.com/kb/128642
values 0,1,2 can be set in
HKEY_LOCAL_MACHINE SYSTEM CurrentControlSetControlWindowsErrorMode
2 should disable all error popups.
nämeless ... i already have disabled error reporting, i wrote that in post # 1 in this thread :-)
that is what you're explaining in the above post right ?
but thanks anyway :-)
Sorry, I am getting rusty and blind.
Ok, thanks for the tip.
The server hasn't crashed yet.
Since last crash, I have applied the setting mentioned in post # 12 + 13 in this thread.
If the server doesn't restart after next crash, I will try enabling Win XP compatibility.
But the server operating system IS Windows XP, so why would that be necessary?
I'll try it anyway.
Mission accomplished / problem solved !
I just had a crash, and the server restarted immediately, just like it's supposed to !
So the checklist for Windows XP is :
- set "Restart the server automatically" in "Options" in BFSM
- Disable error reporting
- set HKEY_LOCAL_MACHINE SYSTEM CurrentControlSetControlWindowsErrorMode to 2
- set "Server Monitor Timer Period" to a low value if you want a fast restart