Source: Query TaskScheduler ‘Last Run Result’ and Each Step Outcome

Task Monitoring and Control

• 08/03/2011
• 2 minutes to read

Applies To: Windows Server 2008 R2

The history of a task is tracked by events. These events can be viewed in Task Scheduler for each task to track when the task was registered, run, and when it completed or failed. The progress of a task can be monitored through its history. A task can be controlled by running or stopping the task manually (on-demand).

Events

Event ID	Source	Message
100	Microsoft-Windows-TaskScheduler	Task Scheduler started the “%3” instance of the “%1” task for user “%2”.
102	Microsoft-Windows-TaskScheduler	Task Scheduler successfully finished the “%3” instance of the “%1” task for user “%2”.
111	Microsoft-Windows-TaskScheduler	Task Scheduler terminated the “%2” instance of the “%1” task due to exceeding the time allocated for execution, as configured in the task definition. Increase the configured task timeout or investigate external reasons for the delay.
129	Microsoft-Windows-TaskScheduler	Task Scheduler launched the “%2” instance of the “%1” task with process ID %3.
200	Microsoft-Windows-TaskScheduler	Task Scheduler launched the “%2” action in the “%3” instance of task “%1”.
201	Microsoft-Windows-TaskScheduler	Task Scheduler successfully completed task “%1” , instance “%3” , and action “%2”.
202	Microsoft-Windows-TaskScheduler	Task Scheduler failed to complete the “%2” instance of the “%1” task with action “%3”. The error value is: %4.
203	Microsoft-Windows-TaskScheduler	Task Scheduler failed to launch action “%3” in instance “%2” of task “%1”. The error value is: %4.
323	Microsoft-Windows-TaskScheduler	Task Scheduler stopped the “%2” instance of task “%1” in order to launch new instance “%3” .
327	Microsoft-Windows-TaskScheduler	Task Scheduler stopped the “%2” instance of task “%1” because the computer is switching to battery power.
328	Microsoft-Windows-TaskScheduler	Task Scheduler stopped the “%2” instance of task “%1” because the computer is no longer idle.
329	Microsoft-Windows-TaskScheduler	Task Scheduler stopped the “%2” instance of task “%1” because the task timed out.
330	Microsoft-Windows-TaskScheduler	Task Scheduler stopped the “%2” instance of task “%1” as request by user “%3” .
331	Microsoft-Windows-TaskScheduler	Task Scheduler will continue to execute the “%2” instance of the “%1” task even after the designated timeout, due to a failure to create the timeout mechanism. The error value is: %3.

Related Management Information

Task Scheduler Tasks

Management Infrastructure

Source: Task Monitoring and Control | Microsoft Docs

Source: How can I enable the Windows Server Task Scheduler History recording? – Stack Overflow

Group Policy Administrative Templates Catalog

Source: Group Policy Administrative Templates