task scheduler intermittent corruption

[howie]

We are having intermittent problems with the scheduled tasks. The
result is the our morning jobs don't run. I've been looking at the log
file and I have found something I don't understand. It appears that the
Task Scheduler starts itself up early in the morning, and then our
application jobs' entries' directory pointers are corrupt. Although
interestingly the Windows Backup doesn't seem to have a problem. Here
is an excerpt from the log file. Please take a look and tell me how you
suggest we debug the problem.
(note that on the prior day to this log -- 5/7/2006 -- the scheduler
executed flawlessly)

"Task Scheduler Service"
4.71.2195.6920"Task Scheduler Service"
Exited at 5/8/2006 4:08:01 PM
"Task Scheduler Service"
Started at 5/8/2006 4:09:40 PM
"Task Scheduler Service"
4.71.2195.6920"Task Scheduler Service"
Exited at 5/8/2006 4:24:39 PM
"Task Scheduler Service"
Started at 5/8/2006 4:26:47 PM
"Task Scheduler Service"
4.71.2195.6920"DISASTER LOAD.job" (disaster_load.exe) 5/8/2006 6:00:01
PM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"DISASTER LOAD.job" (disaster_load.exe) 5/8/2006 6:00:01 PM ** ERROR **
Unable to start task.
The specific error is:
0xc0000022: (Unable to find an error message)
Try using the Task page Browse button to locate the application.
"MONDAY BACKUP.job" (NTBACKUP.EXE)
Started 5/8/2006 7:00:00 PM
"MONDAY BACKUP.job" (NTBACKUP.EXE)
Finished 5/8/2006 7:23:59 PM
Result: The task completed with an exit code of (0).
"EOM REPORTS.job" (eom_monitor.exe) 5/8/2006 8:30:01 PM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"EOM REPORTS.job" (eom_monitor.exe) 5/8/2006 8:30:01 PM ** ERROR **
Unable to start task.
The specific error is:
0xc0000022: (Unable to find an error message)
Try using the Task page Browse button to locate the application.
"RX PROVIDER LOAD.job" (rx_provider_load.exe) 5/9/2006 5:00:00 AM **
WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"RX PROVIDER LOAD.job" (rx_provider_load.exe) 5/9/2006 5:00:00 AM **
ERROR **
Unable to start task.
The specific error is:
0xc0000022: (Unable to find an error message)
Try using the Task page Browse button to locate the application.
"INIT.job" (nhplookupzap.exe) 5/9/2006 5:50:00 AM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"INIT.job" (nhplookupzap.exe) 5/9/2006 5:50:00 AM ** ERROR **
Unable to start task.
The specific error is:
0xc0000022: (Unable to find an error message)
Try using the Task page Browse button to locate the application.
"GET NHP FILE.job" (painsgpg.app) 5/9/2006 7:00:00 AM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.

******* Thanks *********
Howie

 

[howie]

This is a correction to my previous entry. Apparently the problem is
that after a system startup, task scheduler doesn't recognize file or
directory pointers. But it will execute a right-click RUN command. Any
help appreciated.
Howie
(e-mail address removed)