Unable to Find a Message for Task Exit Code in Schedlog.txt File (190139)

MORE INFORMATION

Task Scheduler may not be able to find a task exit message for either of the following reasons:

• If the program is written to work with System Agent (SAGE), it returns an exit code that Task Scheduler recognizes and can interpret. If a corresponding registry value does not exist for this code, the Task Scheduler log indicates that a message for the exit code was unable to be found.
  
  Specifically, this can occur in Microsoft Windows 95 or Windows NT 4.0 if Task Scheduler is installed on a computer that has not had System Agent previously installed. SAGE-aware programs such as ScanDisk and Disk Defragmenter return exit codes that Task Scheduler can interpret, but if System Agent was not installed on the computer previously, the corresponding string values for the exit code messages do not exist in the registry.
• If the program is not SAGE-aware, it may still return an exit code when it finishes. When this occurs, the Task Scheduler log also displays the message listed earlier in this article, but there is no way to determine whether or not the exit code should be interpreted by Task Scheduler.

Because the exit codes a program uses can vary, an exit code of (3) may have different meanings for different programs. However, an exit code of (0) normally means that the task completed successfully, and without any errors.



To view the Task Scheduler log, double-click My Computer, double-click Scheduled Task, and then click View Log on the Advanced menu.

The following list shows examples of exit codes:

• (3)
• (fff9)
• (fffe)

For information about exit codes (result codes) and their corresponding messages that are used with some SAGE-aware programs, see the following article in the Microsoft Knowledge Base: