Can Scheduler re-set after "could not run"?

[plh]

I have several computers around here running scheduler on Win2000 to back up CNC
files from a network to the local drive. The task is set to run daily and runs a
batch file with simple copy and in some cases xcopy commands in it. I notice
that when I check up on it, the Status says "could not run" and that it has not
run again after that particular failure. I don't know what condition was
responsible for the failure to run. Is there something I can set that will allow
the scheduler to resume running without my having to intervene? The only way I
have found to fix it is to delete the task and set up a new one.
Thank You,
-Paul H.

 

[Pegasus \(MVP\)]

I have several computers around here running scheduler on Win2000 to back up CNC
files from a network to the local drive. The task is set to run daily and runs a
batch file with simple copy and in some cases xcopy commands in it. I notice
that when I check up on it, the Status says "could not run" and that it has not
run again after that particular failure. I don't know what condition was
responsible for the failure to run. Is there something I can set that will allow
the scheduler to resume running without my having to intervene? The only way I
have found to fix it is to delete the task and set up a new one.
Thank You,
-Paul H.

The "could not run" message is usually caused by an invalid
account/password being used for the task. After specifying
acceptable account credentials, the tasks will run as scheduled.