Hi everyone,

I am running a hand full of L4D and L4D2 servers on my Windows Server 2008
system. Since several weeks now my L4D(main)-folder is filling over and over
with dumpfiles (*.mdmp). I also check every day my system logs for service
crashes (like game server instances) and there are only some few per week.
This means that not every dump file is caused by a crash. So I tried to deal
with the problem.

So far what I know:


   - Every time either when starting the game service or when the L4D
   instance exits from hibernation (a player connects) a dump file is created.
   - The server console prints the following suspicious message:

*steamservice.cpp (229) : Assertion Failed: BOpenService failed (1060)*


#Console initialized.
#Unable to remove e:\valve\left4dead\l4d\left4dead\addonlist.txt!
#Game.dll loaded for "L4D - Co-op - Normal"
Server is hibernating
Queuing heartbeat send to legacy master server.
...
...
steamservice.cpp (229) : Assertion Failed: BOpenService failed (1060)
Queuing heartbeat send to steam master server updater.
...
...
steamservice.cpp (229) : Assertion Failed: BOpenService failed (1060)
   VAC secure mode is activated.
...
...


The same output if the server instance exits from hibernation.

I found some other forum threads but without any solutions.
http://forums.srcds.com/viewpost/78598


Well I have no crashes and since today the dump files are getting deleted by
my scheduled admin script which runs anyway.
But I think it would be cleaner and better if there were no dump files and
assertions in the first place. :)

Can anyone help me?

Thank you.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to