Performance Monitor Displays Only the First of Multiple Instances from a Binary Log (813950)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Server SP3
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
- Microsoft Windows 2000 Professional SP3
SYMPTOMSWhen 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. CAUSEPerformance Monitor recognizes only the first instance of a
process in a log as valid. All other instances are recognized as containing no
data.RESOLUTIONService Pack InformationTo 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 InformationA supported fix is now available
from Microsoft, but it is only intended to correct the problem that is
described in this article. Apply it only to computers that are experiencing
this specific problem. This fix may receive additional testing. Therefore, if
you are not severely affected by this problem, Microsoft recommends that you
wait for the next Windows 2000 service pack that contains this hotfix. To
resolve this problem immediately, contact Microsoft Product Support Services to
obtain the fix. For a complete list of Microsoft Product Support Services phone
numbers and information about support costs, visit the following Microsoft Web
site: 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 typical support costs
will apply to additional support questions and issues that do not qualify for
the specific update in question. 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
WORKAROUNDTo work around this issue, use one of the following methods. Method 1: Create Separate Log Files for Each Instance - On the View menu, click
Log.
- On the Edit menu, click Add To
Log.
- 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.
- Add the counters that you want for the first instance of
the process that you want to track.
- Save the log file.
- Start the log.
Repeat these steps for each instance of the process that you
want to track. Method 2: Log All InstancesWhen you create the log, select All instances
instead of selecting individual process counters. Method 3: Save Log File in CSV FormatWhen 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. STATUSMicrosoft
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.
Modification Type: | Minor | Last Reviewed: | 10/10/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbSysAdmin kbWin2kSP4fix kbWin2000preSP4Fix kbfix kbbug KB813950 |
---|
|