Event ID 327 — Task Monitoring and Control
Applies To: Windows Server 2008
.jpg)
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).
Event Details
| Product: | Windows Operating System |
| ID: | 327 |
| Source: | Microsoft-Windows-TaskScheduler |
| Version: | 6.0 |
| Symbolic Name: | STOPPING_ON_BATTERIES |
| Message: | Task Scheduler stopped the "%2" instance of task "%1" because the computer is switching to battery power. |
Resolve
Fix task configuration settings
The task was stopped due to a configured setting. Possible causes include:
- The task ran for longer than the maximum configured run time.
- The task was configured to stop when the computer switched to battery power.
- The task was configured to stop when the computer is no longer idle.
- The task was configured to stop when a new instance of the task is triggered.
This behavior might be as expected. However, if the behavior was unexpected you can reconfigure the task configuration settings.
To update the task settings and conditions:
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 configure by locating the task in the task folder hierarchy. Right-click the task, and select Properties.
4. On the Settings and Conditions tabs, update the task settings and conditions.
5. Click OK.
Verify
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.