Event ID 112 — Task Properties

Event ID 112 — Task Properties

Updated: December 6, 2007

Applies To: Windows Server 2008

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.

Event Details

Product: Windows Operating System
ID: 112
Source: Microsoft-Windows-TaskScheduler
Version: 6.0
Symbolic Name: JOB_NO_START_WO_NETWORK
Message: 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.

Resolve
Change task configuration settings

A new task instance was not run because a condition, or a setting defined for the task, was not met. Possible conditions affecting the start of a task include:

  • The task was configured to run only when a specified network is available.
  • The configured expiration time for the task has passed.
  • The task is configured to ignore or queue a new task instance if a previous instance is still running.
  • The task is configured not to run when the computer is on battery power.
  • The task is configured to run only if a specific user is logged on.
  • The task was disabled by a user.
  • The previous task instance might have been running longer than expected because a component is busy processing data. If the task is normally expected to run for this length of time, consider modifying the task triggers to take this run-time length into consideration, or configure the task to be terminated after a preset time.

This behavior may be intentional. However, if you did not intend for the task to run with these conditions, consider changing the corresponding task configuration settings to allow the task to run as intended.

To configure 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. Locate the task to update in the task folder hierarchy, and right-click the task and select Properties. 

4. The Settings tab contains a setting for stopping the task after a set period of time. You can change the task settings on this tab, and you can also update the task configuration settings on the Conditions tab.

5. Click OK.

Verify

To verify that the task runs correctly:

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 that you want 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 to view task events and verify the selected task started successfully.

6. Similarly, verify that the task starts as expected when its defined trigger fires.

Related Management Information

Task Properties

Management Infrastructure

Related:

A fatal internal MTA error occurred. Queue creation failure for queue . Contact Microsoft Technical Support. [ ] (16)

Details
Product: Exchange
Event ID: 112
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: A fatal internal MTA error occurred. Queue creation failure for queue <name>. Contact Microsoft Technical Support. [<value> <value> <value> <value>] (16)
   
Explanation

The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.

   
User Action

If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk. Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

There is not enough space on the disk.

Details
Product: Windows Operating System
Event ID: 112
Source: Kernel
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_DISK_FULL
Message: There is not enough space on the disk.
   
Explanation

The disk being written to has no more room.

   
User Action

Delete some unwanted files from the disk and retry the command.

Related:

Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema propagation on MDB startupHRESULT = .

Details
Product: Exchange
Event ID: 112
Source: EXOLEDB
Version: 6.5.6940.0
Component: Microsoft Exchange OLE DB Provider
Message: Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema propagation on MDB startupHRESULT = <value>.
   
Explanation

The system failed to register event binding on the schema folder. Extensible Markup Language (XML) updates to this folder will not be processed as schema elements.

   
User Action

Contact Microsoft Product Support Services.

Related:

Machine Check Event reported is a CPU thermal throttling event reported from CPU %1. The CPU has dropped below the temperature limit and throttling has been removed. %2 additional error(s) are contained within the record.

Details
Product: Windows Operating System
Event ID: 112
Source: WMIxWDM
Version: 5.2
Symbolic Name: MCA_INFO_CPU_THERMAL_THROTTLING_REMOVED
Message: Machine Check Event reported is a CPU thermal throttling event reported from CPU %1. The CPU has dropped below the temperature limit and throttling has been removed. %2 additional error(s) are contained within the record.
   
Explanation

The temperature of the CPU specified in the event has decreased and the CPU is now running at normal speed. For detailed information about the hardware that caused the problem, refer to the event log.

   
User Action

No user action is required.

Related:

Failed to enable MDB %1 (GUID = %2) because its search index was in an unknown status (%3). Reset the index files by running the command ResetSearchIndex.ps1 in the Exchange Management Shell.

Details
Product: Exchange
Event ID: 112
Source: MSExchange Search Indexer
Version: 8.0
Symbolic Name: SearchIndexUnknownStatus
Message: Failed to enable MDB %1 (GUID = %2) because its search index was in an unknown status (%3). Reset the index files by running the command ResetSearchIndex.ps1 in the Exchange Management Shell.
   
Explanation

This Error event indicates that the Microsoft Exchange Search service did not enable the specified mailbox database because its catalog has an unknown status (mentioned in the event description). The catalog or index files are located in the same directory as the mailbox database. The problem might occur when the index files are corrupted. Because of this error, online mode search may take a long time to return results for users who have mailboxes on the affected mailbox database.

   
User Action

To resolve this error, do one or more of the following:

  • Delete the index files by running the following script from the Exchange Management Shell and let Exchange Search rebuild the index files for the mailbox database. Follow these steps:

    1. Open Exchange Management Shell and locate the script directory under the Exchange server installation root directory (for example: \Program Files\Microsoft\Exchange Server\Scripts).

    2. Type this command: ResetSearchIndex.msh -force <dbname>

      For example:

      [PS] D:\Program Files\Microsoft\Exchange Server\Scripts\ResetSearchIndex.msh -force “Mailbox Database”

      Note   The <dbname> would be the name of the affected mailbox database for which you are resetting the index files. The parameter -force will reset the index files without asking for a confirmation. After several minutes, Exchange Search will re-create the index files for the mailbox database.

  • Get additional help by posting the issue at Newsgroups: Exchange Server and Outlook.

  • If the issue persists, contact Microsoft Product Support Services. For more information, visit the Contact Us page of the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: