SCHEDULED TASK DOES NOT RUN
Description: Task Scheduler is automatically installed with the Microsoft® Windows® Server 2003 family, Windows XP, and Windows 2000 operating systems and is started each time the operating system is started. It can be run through the Task Scheduler graphical user interface or the AT.EXE command.
With the Task Scheduler you can:
- Create tasks.
- Schedule a task to run at a specific time or when a specific event occurs.
- Change the schedule for a task.
- Customize how tasks run.
- Stop a scheduled task.
Scoping the Issue: If Scheduled Tasks fail to run at all, check the following to help narrow down the scope:
Check to see if the Task Scheduler service is in a Starting state, or you cannot Stop the service. If this is the case, check the permissions on the Windows\Tasks folder. If the service account cannot access this folder to update the SchedLgU.txt file, it will fail to start.
Compare the following registry key with a known good machine: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule
Check the permissions on the All Users\Application Data folder. The computer account needs to have read/write access to this folder. If there is folder redirection implemented, the permissions may not be set properly
The Task Scheduler service must be running and properly configured to run tasks. If you had stopped scheduled tasks manually from the Scheduled Tasks window, the service stops and does not initialize the next time you start the computer. If the service is not configured to log on as the local system account, it may not start.
To check the settings for the service:
- Click Start, click Control Panel, and then double-click Administrative Tools.
- Click Computer Management.
- Expand Services and Applications, and then click Services.
- Right-click the Task Scheduler service, and then click Properties.
- On the General tab, make sure that the startup type is set to automatic, and that the service status is Started. If the service is not running, click Start.
- On the Log On tab, make sure that the local system account is selected, and that the Allow service to interact with desktop check box has a check mark.
- Click OK, and then quit Computer Management.
Data Gathering: In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done.
Troubleshooting / Resolution:
- Verify if the service is started, disabled or stuck in a starting state. Ensure it is set to start automatically and is configured to use the Local System Account.
- If the service is running but no tasks are successful, try creating a simple task like running Notepad.exe or Calc.exe and executing it manually
- If creating a new task and running it manually works, try to run another task manually
- MSDN: Task Scheduler Best Practices
- Microsoft KB Article 329769: Scheduled tasks may not run in Microsoft Windows XP
- Microsoft KB Article 812400: Scheduled tasks may not run and generate an exit code of 80
- Microsoft KB Article 843280: Non-interactive At.exe tasks do not run in Windows Server 2003
- Microsoft KB Article 843537: Scheduled tasks that you create and rename by using the at command may not run correctly on a computer that is running Windows 2000 with Service Pack 4
- Microsoft KB Article 956519: A scheduled task may not run after it wakes a Windows Vista-based or a Windows Server 2008-based computer from hibernation
- Microsoft KB Article 933550: Scheduled tasks that ran before you uninstall Windows Server 2003 SP2 may no longer run after the uninstall is complete
- Microsoft KB Article 899649: The Task Scheduler service may not start scheduled tasks on a Windows Server 2003-based computer