Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a scheduled task on a Windows Server 2000 box which is scheduled to run daily. On Monday, the task ran perfectly in that the thing it fires off (a console application) completed, but the scheduled task itself is still marked as "Running" on the Scheduled Tasks window. So both yesterday and today the job did not fire.

The underlying process isn't present, the same console application is run by numerous other scheduled tasks with different arguments at other times and they've completed tidily.

Unfortunately the scheduled tasks log (Scheduled Tasks > Advanced > View Log) doesn't show enough history to show when this job ran.

When I right click on the task and select End Task it has no effect (the option to Run is disabled).

I'd like to be able to re-use this scheduled task, but more than that I want to understand what might have caused this issue so as to try to ensure that it doesn't happen again.

share|improve this question

You could try restarting the windows task scheduler service, but sometimes rebooting a Windows box will solve all your problems ;-)

share|improve this answer
Yeah, that's what I was fearing. It's a production box with lots hanging off it, I'd prefer to avoid a complete reboot ... – Unsliced Aug 11 '10 at 20:34
IIRC 'no more scheduled reboots' was one of the slogans used for advertising W2K to NT 4 users – james Aug 14 '10 at 2:59

When the job terminates, it attempts to update itself indicating (a) the date last run and (b) reset the job status to blank. To do this, it must have full control of the job file. If another process attempts to access the job file (most likely culprit being the antivirus software), the job file will be busy and will not be updated.

The best thing to do is to disable the antivirus scanning of c:\windows\tasks.

Hope this is some help.

share|improve this answer
This article has a lot more information about how to diagnose and correct this issue. – Malcolm Aug 15 '14 at 16:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.