The Log File in the Task Scheduler May Be Incorrectly Formatted and Difficult to Read (303204)



The information in this article applies to:

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional

This article was previously published under Q303204

SYMPTOMS

In the Task Scheduler service, when you click View Log on the Advanced menu, some of the text that is contained in the log file (Schedlgu.txt) may be incorrectly formatted and difficult to read.

CAUSE

This problem can occur if you upgrade your computer from Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows 98 Second Edition, or Microsoft Windows Millennium Edition (Me) while you are using the Scheduled Tasks feature.

RESOLUTION

To resolve this problem, replace the log file:
  1. Click Start, click Run, and then in the Open box, type: msconfig.
  2. Click Selective Startup, and then click to clear the Load System Services check box.
  3. Click OK, and then click Restart to restart the computer when you are prompted.
  4. After the computer restarts, a System Configuration Utility message is displayed. Click OK to close the message. Then, the System Configuration Utility window is displayed. To close the System Configuration Utility window, click the X in the upper-right corner of the program window (the Close button).
  5. Click Start, and then click Search.
  6. Click All files and folders.
  7. Click More Advanced Options, and then click to select the Search system folders check box.
  8. In the All or part of the file name: box, type: schedlgu.txt.
  9. Click Search.
  10. Right-click the Schedlgu.txt file, and then click Delete.
  11. To close the Search window, click the X in the upper-right corner of the window (the Close button).
  12. Click Start, click Run, and then in the Open box, type: msconfig.
  13. Click Normal Startup, and then click OK.
  14. When you are prompted, click Restart to restart the computer. Windows automatically creates a new log file that contains properly formatted and readable text.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:1/15/2006
Keywords:kbprb KB303204