Event ID 408 — Idle Trigger Task Registration
Updated: August 5, 2011
Applies To: Windows Server 2008 R2
Tasks can be started when the computer enters an idle state by defining an idle trigger or setting the idle conditions for when the task starts. To create a task with an idle trigger, register the task with the Task Scheduler service.
|Product:||Windows Operating System|
|Message:||Task Scheduler service failed to initialize idle state detection module. Idle tasks may not be started as required. Additional Data: Error Value: %1.|
Use the error code to diagnose idle state module failure
Use the error code provided in the event to further diagnose the reason for the idle state module initialization failure. Ensure that there is sufficient free memory on the computer. To free memory, close some applications. To find a description of the error code provided in the event, convert the error code into decimal form and then find the error code in the list of system error codes on http://go.microsoft.com/fwlink/?LinkId=102313.
To register a task that will run only if the computer is idle, and then verify that the task runs as specified:
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. On the General tab, specify a name for the task. On the Actions tab, specify an action for the task. On the Triggers tab, click New, and define a trigger for the task. For more information about triggers and actions, see the Task Scheduler online help at http://go.microsoft.com/fwlink/?LinkId=92609.
4. On the Conditions tab of the task, select the condition to Start the task only if the computer is idle for and specify the associated parameters.
5. Click OK.
6. Verify that no errors are reported when the task is created by selecting the newly created task and then clicking the History tab. Verify that it does not show any partial registration failures for the task.
- Verify that the task runs at the specified time if the computer has been idle as specified. Verify that the specified action was run, or click the History tab for the task in Task Scheduler to verify that it contains events indicating that the task was started successfully.