Task Scheduler Failure - The Next Attempt 1

[mwolf00]

I have a task scheduled daily. It calls an asp page which goes to one database to move data into another. It's been running fine for 2 months. About a week ago, there must have been a network problem and the task failed and the scheduler shows "could not start" in the status.

Is there any way to have scheduler just try the task again on the following day (as scheduled)? It seems that the task hasn't run since it failed. Failing one day is not a big deal as the data would be captured the next run. However, failing once stopping the whole works is not great.

Any ideas?

Programming today is a race between software engineers striving to build better and bigger idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rick Cook (No, I'm not Rick)

 

[bcastner]

Do a file search for: schedlgu.txt
Delete the first instance found.
Reboot.

 

[sueb859]

Is there a way to receive some type of email notification if a job fails to start or if the job does not succeed?

 

[bcastner]

Unfortunately, no.

 

[bcastner]

Notify Me of Missed Tasks. Contrary to its name, the Notify Me of Missed Tasks option notifies you only of Task Scheduler's failure, not of individual missed tasks. Tasks that fail to run because of corrupt or missing executables don't kick off a notification.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/maintain/featusability/tsksched.mspx

 

[mwolf00]

Does that mean that if I write a separate task to fnd and remove (or rename) this file, I will not have the problem of one stoppage halting the rest of the schedule?

Programming today is a race between software engineers striving to build better and bigger idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rick Cook (No, I'm not Rick)

 

[mwolf00]

Actually, it seems to have failed because I changed my password... I guess I have to remember to reset it every time I change my password - yuck - but it's better than running it manually every day...

Programming today is a race between software engineers striving to build better and bigger idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rick Cook (No, I'm not Rick)

 

[bcastner]

Yes, or blank passwords:

http://support.microsoft.com/?kbid=310715

http://support.microsoft.com/defaul...port/kb/articles/q311/1/19.asp&NoWebContent=1

For that reason I schedule all tasks under a created artificial account without password expiration. If you need access to network resources you cannot depend on the local account; so create an account with suitable priviliges and use the runas credentialling for this account whose password never dies.

If this seems too large a security breach, then use the logon scripting features and the AT command to schedule the task. In that case you can use script encryption or other means to hide the plain text username and password. One option:

http://www.commandline.co.uk/sanur/

Second option:

http://www.tek-tips.com/viewthread.cfm?SQID=676827&SPID=779

But usually I just lock down the artificial Scheduled Task user and use those credentials for every task.