Microsoft KB Archive/883499

= System Monitor may restart on delayed intervals on Windows 2000 =

Article ID: 883499

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Advanced Server

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
On a computer that is running Microsoft Windows 2000, when you schedule System Monitor to start new performance logs after certain intervals, each new log may not start at the correct time. Instead, each new log may start one sample interval later.

For example, if you configure System Monitor to start a new log after 24 hours, and you set a sample interval of 10 minutes, each day the new log may start 10 minutes later than the time that the previous log started. After 30 days, the new log may start five hours later than you expect.



RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version        Size    File name ---  05-Aug-2004  17:54  5.0.2195.6966  86,288  Smlogsvc.exe After you install the preceding hotfix, you must create the EmulateXPRestart registry subkey. To do this, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK. Locate and click the following registry subkey:

 On the Edit menu, point to New, and then click DWORD Value. In the right pane, click New Value # 1, type EmulateXPRestart, and then press ENTER. Right-click EmulateXPRestart, and then click Modify. In the Value box, type 1, and then click OK.</li> Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
After you apply this hotfix, System Monitor in Windows 2000 behaves like System Monitor in Microsoft Windows XP and in Microsoft Windows Server 2003. New logs do not exhibit the behavior that is mentioned in the &quot;Symptoms&quot; section. However, new logs may be delayed for up to two minutes. This delay occurs because System Monitor must compete with other processes for computer resources. Creating a new log file adds an additional workload to your computer. If the computer is busy during the time that a new log file is created, a delay may occur in the start time for the new log. For additional information about the new file naming schema for Microsoft Windows software update packages, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For additional information about the terminology that is used in this article, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: perfmon sysmon performance monitor

Keywords: kbperfmon kbbug kbfix kbwin2000presp5fix kbhotfixserver kbqfe KB883499

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.