Event ID 203 — Task Monitoring and Control
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).
|Product:||Windows Operating System|
|Message:||Task Scheduler failed to launch action "%3" in instance "%2" of task "%1". The error value is: %4.|
Use error code to identify the action failure
Use the error code provided in the action failure event to further identify reasons for a task action failing to execute.
Task Scheduler error codes:
A task trigger is not found. Try to edit the task triggers.
One or more of the properties required to run this task have not been set.
There is no running instance of the task.
The Task Scheduler service is not installed on this computer.
The task object cannot be opened.
The object is either an invalid task object or is not a task object.
No account information could be found in the Task Scheduler security database for the task indicated. Set the account information for the task.
Unable to establish existence of the account specified. Set the account information for the task.
Corruption was detected in the Task Scheduler security database; the database has been reset.
Task Scheduler security services are available only on Windows NT.
The task object version is either unsupported or invalid.
The task has been configured with an unsupported combination of account settings and run time options.
The Task Scheduler Service is not running. Start the Task Scheduler service.
The task XML contains an unexpected node.
The task XML contains an element or attribute from an unexpected namespace.
The task XML contains a value which is incorrectly formatted or out of range.
The task XML is missing a required element or attribute.
The task XML is malformed.
The task is registered, but not all specified triggers will start the task.
The task is registered, but may fail to start. Batch logon privilege must be enabled for the task principal.
The task XML contains too many nodes of the same type.
The task cannot be started after the trigger end boundary.
An instance of this task is already running.
The task will not run because the user is not logged on.
The task image is corrupt or has been tampered with.
The Task Scheduler service is not available.
The Task Scheduler service is busy and cannot handle the request. Please try again later.
The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition.
The Task Scheduler service has instructed the task to run.
The task is disabled.
The task has properties that are not compatible with earlier versions of Windows.
The task settings do not allow the task to start on demand.
To verify that the execution of a task has completed as expected:
1. Click the Start button and type **Task Scheduler **in the Start Search box.
2. Select the Task Scheduler program to start Task Scheduler.
3. Select the task to run by locating the task in the task folder hierarchy.
4. On the Actions menu click Run. You can also click Run in the Actions pane.
5. Click the History tab for the task to verify that it contains events indicating the task was registered successfully. Also, ensure that the task completed successfully or that the task timed out as expected.