Event ID 309 — Task Scheduler Engine Communication
Applies To: Windows Server 2008
A Task Scheduler engine communicates with the Task Scheduler service to execute tasks. The service creates a task engine to run tasks.
|Product:||Windows Operating System|
|Message:||There are %1 Task Scheduler tasks orphaned during task engine "%2" shutdown. Find the process run by this task in the Task Manager and stop it manually.|
Clean up orphaned tasks
To clean up orphaned tasks, find the processes representing these tasks in Task Manager and stop them manually.
To stop a task manually:
1. Open Task Manager by pressing CTL+ALT+DELETE** and select **Task Manager.
2. Click the Processes tab.
3. Select Taskengine.exe. This process is a task engine that can run multiple tasks.
4. Click End Process.
Create a task for the user for which the task engine was failing, and ensure that the session events (events 301, 304, 308, 310, 312, 313, 314, 317, 318, 319, and 320) are received throughout session creation and shutdown. The events are logged in the 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.
Click Create Task.
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 new 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, expading the Windows folder, expanding the TaskScheduler folder, and then clicking the Operational event log.
4. Verify that the session events are in the log.