Task Properties

Applies To: Windows Server 2008 R2

Task properties define the settings and conditions for running a task. A task will run if all of its conditions are met after the task is triggered to start. Conditions are divided into three categories: idle conditions, power conditions, and network conditions. The conditions for a task care displayed on the Conditions tab of the Task Properties or the Create Task dialog box in Task Scheduler.

Task settings specify how a task is run, stopped, or deleted. The settings for a task are displayed on the Settings tab of the Task Properties or the Create Task dialog box in Task Scheduler.

Events

Event ID Source Message

101

Microsoft-Windows-TaskScheduler

Task Scheduler failed to start the "%1" task for user "%2". The error value is: %3.

103

Microsoft-Windows-TaskScheduler

Task Scheduler failed to start the "%2" instance of the "%1" task for user "%3". The error value is: %4.

104

Microsoft-Windows-TaskScheduler

Task Scheduler failed to log on "%1". The failure occurred in "%2". Ensure the credentials for the task are correctly specified. The error value is: %3.

107

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%2" instance of task "%1" due to a time trigger.

108

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%2" instance of task "%1". The task was triggered by an event trigger.

109

Microsoft-Windows-TaskScheduler

Task Scheduler launched "%2" instance of task "%1" due to a registration trigger.

110

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%2" instance of task "%1" for user "%3" .

112

Microsoft-Windows-TaskScheduler

Task Scheduler could not start task "%1" because the network was unavailable. Ensure the computer is connected to the required network as specified in the task. If the task does not require network presence, remove the network condition from the task configuration.

114

Microsoft-Windows-TaskScheduler

Task Scheduler could not launch task "%1" as scheduled. Instance "%2" is started now as required by the configuration option to start the task when available, if the scheduled time is missed.

117

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%2" instance of task "%1" due to an idle condition.

118

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%2" instance of task "%1" due to system startup.

119

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" logon.

120

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" connecting to the console.

121

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" disconnecting from the console.

122

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" remotely connecting.

123

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" remotely disconnecting.

124

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" locking the computer.

125

Microsoft-Windows-TaskScheduler

Task Scheduler launched the "%3" instance of task "%1" due to user "%2" unlocking the computer.

126

Microsoft-Windows-TaskScheduler

Task Scheduler failed to execute the "%1" task. Task Scheduler is attempting to restart the task. The error value is: %2.

127

Microsoft-Windows-TaskScheduler

Task Scheduler failed to execute task "%1" due to a shutdown race condition. Task Scheduler is attempting to restart the task.

128

Microsoft-Windows-TaskScheduler

Task Scheduler did not launch task "%1" because the current time exceeds the configured task end time. Extend the end time boundary for the task if required.

130

Microsoft-Windows-TaskScheduler

The Task Scheduler service failed to start the "%1" task due to the service being busy. The error value is: %2.

142

Microsoft-Windows-TaskScheduler

User "%2" disabled Task Scheduler task "%1"

145

Microsoft-Windows-TaskScheduler

Task Scheduler woke up the computer to run a task.

204

Microsoft-Windows-TaskScheduler

Task Scheduler failed to retrieve the event triggering values for task "%1" . The event will be ignored. Additional Data: Error Value: %2.

205

Microsoft-Windows-TaskScheduler

Task Scheduler failed to match the pattern of events for the following task: "%1" . The events will be ignored. The error value is: %2.

305

Microsoft-Windows-TaskScheduler

Task Scheduler did not send the "%1" task to task engine "%2" . The error value is: %3.

322

Microsoft-Windows-TaskScheduler

Task Scheduler did not launch task "%1" because instance "%2" of the same task is already running.

324

Microsoft-Windows-TaskScheduler

Task Scheduler queued the "%2" instance of task "%1" and will launch it as soon as instance "%3" completes.

326

Microsoft-Windows-TaskScheduler

Task Scheduler did not launch task "%1" because the computer is running on batteries. If launching the task on batteries is required, change the respective flag in the task configuration.

332

Microsoft-Windows-TaskScheduler

Task Scheduler did not launch the "%1" task because user "%2" was not logged on when the launching conditions were met. Ensure the user is logged on or change the task definition to allow the task to launch when the user is logged off.

Task Scheduler Tasks

Management Infrastructure