Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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 Windows Server 2008 SP 2 Task Scheduler task that should run every 10 minutes.

enter image description here

The trigger says "At 6:50 PM every day - After triggered, repeat every 10 minutes indefinitively."

Looking at the Next Run Time, it says 6/18/2012 8:00 PM. However, when I let that time pass, the Next Run Time just changes to 8:10 PM but the task has not started and the Last Run Time is unchanged from yesterday. Last Run Result is "The operation completed successfully. (0x0)".

It worked when I first created it a few days ago, but today I disabled then re-enabled it and now it just won't start automatically. I can still manually trigger it and that works.

How can I get this task to automatically run every 10 minutes when enabled no matter what?

share|improve this question
How do you know that the task has not run at that interval? Often a task that runs fine from a command prompt will not work from a scheduled task because of one of many different reasons. Credentials that don't have permissions, or no credentials at all, or no "start in" path, or relative paths being used when they shouldn't, etc. Point is, maybe the task is starting, but is also ending immediately. – Mark Henderson Jun 19 '12 at 3:14
The task has executed in the past fine as indicated in the History tab of TS. I just noticed the issue today when I disabled the task then re-enabled it. Looking at the History tab, it's no longer starting at the time indicated in the Next Run Time. I keep refreshing the view and the Next Run Time just updates to 10 minutes later but nothing happened (Last Run Time and Last Run Result are not updated). – Dan C Jun 19 '12 at 3:41
I rebooted the server and, what do you know, the tasks are working now! Looks like Task Scheduler needed a good kick in the pants. I will keep an eye and update here. – Dan C Jun 19 '12 at 19:16

Probably too late to be any help on this 3-year old topic.

On the General tab make sure you choose the "Run whether user is logged on or not" option.

The default setting is "Run only when user is logged on" which means the task will not run until someone logged on to the server.

share|improve this answer

Check the job start date/time. This can trip you up (it has snagged me before).

share|improve this answer
The job is set to Start 6/13/2010, 6:50 PM. Since today is the 18th, I don't think that's the issue. – Dan C Jun 19 '12 at 4:58
At least I hope that's not the issue. I would hate to have to change the date and time every time I disable/reenable the task. I didn't have to do that in Windows Server 2003 Task Scheduler. – Dan C Jun 19 '12 at 5:20

I think you want to set the task to run once every 10 minutes for 24 hours as you are triggering it to repeat once daily. so it would run daily, repeating every 10 minutes for 24 hours and then repeating the process.

screen cap from task scheduler

Might also need to set the "Stop task if it runs longer than" option under "Settings" for the task. Might be skipping the scheduled task because task scheduler thinks the task is still running when it is not...

share|improve this answer

This may not be relevant now, but in case you enable\disable scheduled task(s) manually you can use an option of starting the task asap after the scheduled start was missed. enter image description here

share|improve this answer

Do you have Windows Live installed? I was pulling my hair out over this, but then found if you disable the Windows Live \ SOXE task everything comes back to life

share|improve this answer

My fix was simple... I had already manually ran the scheduled task, but I created the scheduled task for the intent of using it daily... I had several TB to copy over to a backup server so I could not schedule the task just yet. My fix was to update the Start date to the current day, and that for some reason resolved it. Detailed info: Previous start date was Jan 3 which was when I created the task and manually ran it. The task was enabled to run daily and failed on Jan 5th. Went into the settings and updated the date to the current day (Jan 6), ran that night and completed on Jan 7). Location: Server 2012 R2, Task Scheduler, Open task, Triggers Tab, Open Trigger, Update Start Date to current day.

Hope this helps others.

share|improve this answer

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.