On a client's computer running Windows XP
I have a task scheduled to run at 2:00 AM on Tuesday through Saturday.
The task is a batch script (.bat file).
It has been running fine for years.
After a scanner was installed on the system (by someone else) about a month ago, it stopped working. (I'm not sure if the failure started IMMEDIATELY after the scanner was installed, but it is the only thing my client could think of that happened at about the same time.)
But it still works occasionally, e.g. for the first few days of October it ran.
On the scheduled tasks window (on a day when it did NOT work):
the Last Run Time is shown as 2:00 AM
the Last Result is 0xff
If when at the computer during the day I change the scheduled time to be in a two minutes, then wait two minutes, it runs fine.
In the scheduler log file c:\windows\SchedLgU.txt
- the task is logged as starting AND finishing at 2:00 AM
- the completion code of 0xff is logged.
In the task scheduler Task / Run field, I specify just the full name of the batch file.
The batch file:
- begins with multiple comment lines starting with "::" on each line
- the first executable statement is "call setymd.bat"
- setymd.bat is located in the same folder
- the first thing setymd.bat does is create a small text file
- that text file does NOT get created when the task does not run
Hence I conclude that the failure occurs before the batch file even starts, e.g. perhaps during cmd.exe startup.
The computer is left on all night, and I believe it does not go into a
sleep mode. (I have checked the "wake the computer.." option, just in case.)
Does anyone have any ideas of what might be causing this failure?