I don't think Alper's issue is the same. They have it running for several days and then it stops. You restart the server and the job doesn't start. This doesn't sound like the same problem to me. I believe your problem is more difficult to troubleshoot. There must be something in the system environment or initial setup that prevents the batch from starting after reboot. In comparison if you start the service manually, everything seems to work. Right? So what is the difference then? When the service starts automatically after reboot, what is missing? Does the batch file reside on a network share? What about the scheduler service? Is that installed on a local drive or network share? Do you have HTML logs option turned on? If yes, where are the report files created? Are they updated after message appears in schedule.log about the job being starting? : The problem I reported yesterday (24x7 batch job fails
: to start after server reboot) sounds very much like the
: problems being reported by Alper (24x7 exits unexpectedly)
: and by Salvo (24x7 don't work). So far, none of the suggestions
: has helped in my case. I am running 3.4.26 and have never
: had a different version.
|
