I'm experiencing a problem with a scheduled batch job
not running after the Windows 2003 server is
rebooted or shut down. Services are started and
the log shows the job starts but never finishes.
When this happens I have to save the jobs again and
then they run fine. Job is scheduled to run 1x every hour,
every day. The server is virtualized. Any ideas as to
why this would be occuring and what I should look at
to resolve this problem. Thanks.

Not sure what could be causing that. I suggest that for beginning you add some echo commands to the batch file and schedule the file with output redirection to a file, something like

cmd /C C:\batches\mybatch.bat > C:\batches\mybatch.log

#####yze the log file after start and check if anything is written to it. If yes, check where it gets stuck. If nothing appears in the file, it means the batch file isn't started. So it could be a file path isue or the current working directory that affects the job running. After you save jobs the current working directory possibly changes and things start running ok. Please note that for all services the default working directory is C:\Windows\System32

: I'm experiencing a problem with a scheduled batch job
: not running after the Windows 2003 server is
: rebooted or shut down. Services are started and
: the log shows the job starts but never finishes.
: When this happens I have to save the jobs again and
: then they run fine. Job is scheduled to run 1x every hour,
: every day. The server is virtualized. Any ideas as to
: why this would be occuring and what I should look at
: to resolve this problem. Thanks.

: Not sure what could be causing that. I suggest that for beginning you add
: some echo commands to the batch file and schedule the file with output
: redirection to a file, something like

: cmd /C C:\batches\mybatch.bat > C:\batches\mybatch.log

: #####yze the log file after start and check if anything is written to it. If
: yes, check where it gets stuck. If nothing appears in the file, it means
: the batch file isn't started. So it could be a file path isue or the
: current working directory that affects the job running. After you save
: jobs the current working directory possibly changes and things start
: running ok. Please note that for all services the default working
: directory is C:\Windows\System32

: Not sure what could be causing that. I suggest that for beginning you add
: some echo commands to the batch file and schedule the file with output
: redirection to a file, something like

: cmd /C C:\batches\mybatch.bat > C:\batches\mybatch.log

: #####yze the log file after start and check if anything is written to it. If
: yes, check where it gets stuck. If nothing appears in the file, it means
: the batch file isn't started. So it could be a file path isue or the
: current working directory that affects the job running. After you save
: jobs the current working directory possibly changes and things start
: running ok. Please note that for all services the default working
: directory is C:\Windows\System32

Thanks for your reply. I am writing to a log file and can
confirm that the batch file is not started. Default working
directory is C:\Windows\System32. I'll keep testing to see
if I can find any other issues with directories. Thanks again.