Server side request
Balmark
Join Date: 2002-11-01 Member: 3476Members, Constellation, Reinforced - Silver, Reinforced - Shadow, WC 2013 - Shadow
<div class="IPBDescription">(error free shutdown?)</div>Hey,
I've a schedule running to kill the server and restart it after doing an update, this happens every night .. or should
I dont get to check the server often.. but when I do, its not a happy picture
Killing the scheduled job occasionally results in an error window from Server.exe
The Instruction at "0x1053caa9" referenced memory at "0x0000002c". The memory could not be "read"
Click on OK to terminate the program
Problem is, this messes up automation for keeping an updated server running automatically.. for me anyhow ;)
Server.exe gets locked, the update doesnt succeed and server.exe cant re-run
Is there some hook can be called to shutdown via another command prompt or a way to set server.exe to shutdown error free either from a startup parameter (ie. have a startup parameter to only run the server for 23.5 hours) or just repress any errors?
Thanks,
Bal
I've a schedule running to kill the server and restart it after doing an update, this happens every night .. or should
I dont get to check the server often.. but when I do, its not a happy picture
Killing the scheduled job occasionally results in an error window from Server.exe
The Instruction at "0x1053caa9" referenced memory at "0x0000002c". The memory could not be "read"
Click on OK to terminate the program
Problem is, this messes up automation for keeping an updated server running automatically.. for me anyhow ;)
Server.exe gets locked, the update doesnt succeed and server.exe cant re-run
Is there some hook can be called to shutdown via another command prompt or a way to set server.exe to shutdown error free either from a startup parameter (ie. have a startup parameter to only run the server for 23.5 hours) or just repress any errors?
Thanks,
Bal
Comments
devicenull .. I love you :)
This is perfect :) Simplest solution for me, lets me just run a task for 23.5 hours, run a server update and start the service again :)