Performance Monitor Displays Only the First of Multiple Instances from a Binary Log

This article has been archived. It is offered "as is" and will no longer be updated.
When you use the Performance Monitor snap-in (Perfmon.msc) to create a binary (.blg) PerfMon log that shows multiple instances of a particular process, only the first instance can subsequently be displayed on the chart.
Performance Monitor recognizes only the first instance of a process in a log as valid. All other instances are recognized as containing no data.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The Global version of this fix has the file attributes (or later) 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   ----------------------------------------------------------   30-Jan-2003  08:53:38   5.00.2195.6660 151,824   Pdh.dll				

To work around this issue, use one of the following methods.

Method 1: Create Separate Log Files for Each Instance

  1. On the View menu, click Log.
  2. On the Edit menu, click Add To Log.
  3. In the Add To Log dialog box, type the name of the computer that you want to monitor in the Computer box. For example, type \\computername.
  4. Add the counters that you want for the first instance of the process that you want to track.
  5. Save the log file.
  6. Start the log.
Repeat these steps for each instance of the process that you want to track.

Method 2: Log All Instances

When you create the log, select All instances instead of selecting individual process counters.

Method 3: Save Log File in CSV Format

When you create the log file, the default format for the file is Binary. Instead, use the Text File (Comma delimited) option. This option creates a log file in the Comma Separated Value (.csv) format.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Article ID: 813950 - Last Review: 02/27/2014 21:16:49 - Revision: 2.9

Microsoft Windows 2000 Server, Microsoft Windows 2000 Server SP1, Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Professional SP1, Microsoft Windows 2000 Professional SP2, Microsoft Windows 2000 Service Pack 3

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbsysadmin kbwin2ksp4fix kbwin2000presp4fix kbfix kbbug KB813950