I remember one of the problems with running a Windows server was that if a fatal error occurred, there would be a crash dialogue and you would have to click "ok" - while on Linux the server would simply restart automatically without user intervention. (Unless the server freezes instead of a normal crash.) There's this parameter -nocrashdialog which is meant for clients, but I have seen server owners using it in their start-up line so it might help (along with -console naturally).

ServerDoc might also help, but not sure if it can cover all situations.

And then there's ServerChecker - might also be worth checking out.

Maybe you already know all of this, but then there's the fun server being off-line since 20 hours.

thank you for the suggestions pizzahut, we have tried both before but with no luck. im going to try something else to solve this issue with our Win Dedi and will hopefully solve this issue..

all servers should be up now

Thanks for the tips pizzahut, nice to see you still around! You still playing TFC?

Did you manage to try any of those btw? We tried before without much luck, maybe we did something wrong!

i have hopefully solved this issue with the Memory Crash Error PopUp and Servers should auto restart if they crash or get a memory error..

amigaoasis wrote:
Did you manage to try any of those btw? We tried before without much luck
MadMax wrote:
Memory Crash Error PopUp
I think ServerChecker was reliable, but it's a long time ago when RV was running on Windows, so I'm not sure if ServerChecker helps against memory error popups. And ServerDoc might have improved since then. I never tried FireDaemon.

AFAIR one of these tools requires admin rights - probably ServerChecker, but I can't say for sure.

all it needed was a quick registry edit and it was sorted, the only time they will crash is if the model precache goes over 512 limit hl1/tfc side.

Did you try ServerChecker? I just ran it on my local PC, deliberately caused a fatal error (512 item count limit) by changing to a map from the WON era (nightshift_r), and it detected that the HLDS didn't respond, closed it together with the fatal error message and restarted it. Can't say how it would fare with a memory error though.

img836.imageshack.us/img836/6290/serverchecker.png

Btw the Steam Service Start message comes up if I don't have the Steam client running - not sure if/why it's needed. (It's a standalone DS, not Steam Tools.)

I think we had a few problems with programs like this, we need them to run while user is either Logged Off / Remote Desktop Session Ended , some programs wont run once you end a Remote Desktop session or Log Off and you have to Log back in to click OK for the server to restart on the errors abit of a pain.. im 100% sure there is a module out there for MetaMod that by passes the 512 precache Limit, might not have been released but im sure its been done.