Event ID 311 — Task Scheduler Engine Launching
Applies To: Windows Server 2008
A task engine starts when a task is run for a specified principal (the security context the task runs under).
|Product:||Windows Operating System|
|Message:||Task Scheduler failed to start the "%1" task engine process due to an error occurring in "%3". The command is: "%2" . The error value is: %4.|
Use error code to identify the action failure
A failure occurred when the Task Scheduler attempted to start a task engine to run a task. Use the error code provided in the failure event to identify the cause of the failure. The following list contains information about possible error codes. The problem may also have been transient. In that case, retry the operation by attempting to restart the task that was trying to run.
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 runtime 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.
Create a task for the user for which the task engine was failing to start and ensure that event 300, which indicates that the session started successfully, is logged in the Microsoft-Windows-TaskScheduler/Operational event log.
To define a task and register a task:
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. Click Create Task.
4. On the General tab, define a name for the task. On the Triggers tab, add a trigger to the task. On the Actions tab, define an action for the task.
5. Click OK, and verify that no errors are reported when the task is created.
6. Select the newly created task and verify on the History tab that there are not any partial registration failures for the task.
To verify that events are in the Task Scheduler event log:
1. Click the Start button and type **Event Viewer **in the Start Search box.
2. Select the Event Viewer program to start Event Viewer.
3. Locate the Microsoft-Windows-TaskScheduler/Operational event log by expanding the Applications and Services Logs folder, expanding the Microsoft folder, expanding the Windows folder, expanding the TaskScheduler folder, and then clicking the Operational event log.
4. Verify that the event 300 is in the log.