FIX: Error message when you run the SQLDiag utility or the PSSDiag utility: "Exception creating Perfmon log" (906532)


The information in this article applies to:

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Workgroup
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Workgroup Edition

SYMPTOMS

When you run the SQLDiag utility or the PSSDiag utility to collect Performance Monitor (PerfMon) counters, you may receive the following error message:
Exception creating Perfmon log
When this problem occurs, an error message that resembles the following message is logged in the ##Sqldiag.log file or in the ##Pssdiag.log file:
2006/07/14 01:36:02.71 PSSDIAG Exception 0xC0000005 caught.
2006/07/14 01:36:02.71 PSSDIAG Creating mini-dump file...
2006/07/14 01:36:02.87 PSSDIAG Mini-dump created
2006/07/14 01:36:02.89 ServerName\* Exception creating Perfmon log. Please see Microsoft Knowledge Base article 906532 for a possible remedy
Note
  • The previous error message is the version for the PSSDiag utility. In the version for the SQLDiag utility, SQLDIAG appears instead of PSSDIAG.
  • The ##Sqldiag.log file is located in the Sqldiag folder. The Sqldiag folder is located in the same folder as the SQLDiag utility. The SQLDiag utility is located in the following folder:

    %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn

  • The ##Pssdiag.log file is located in the Output folder. The Output folder is located in the same folder as the PSSDiag utility. To obtain the PSSDiag utility, visit the following Microsoft download site:

    http://www.microsoft.com/downloads/details.aspx?familyid=5564386a-28c2-4483-8293-76fff67b9eb3

In another scenario, the SQLDiag utility or the PSSDiag utility may unexpectedly stop after an error message that resembles the following message is logged:
2006/06/10 05:05:02.20 ServerName\* Starting Perfmon

CAUSE

These problems occur because of a problem in the Microsoft Windows Performance Data Helper (PDH) library and in the performance extension DLL. Both the SQLDiag utility and the PSSDiag utility use the PDH library to collect Performance Monitor counters. The Performance Monitor counters are provided by the performance extension DLL. This DLL is available through the PDH library.

RESOLUTION

Microsoft Windows 2000

To resolve this problem, obtain the latest service pack for Windows 2000. For more 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

Microsoft Windows XP

Windows XP with Service Pack 2

If you are using Windows XP, and you have applied Windows XP Service Pack 2 (SP2), you can resolve this problem by applying the hotfix that is discussed in the following Microsoft Knowledge Base (KB) article:

917022 A program that uses the Performance Data Helper library to open a performance object may stop responding on a Windows XP-based computer

Windows XP without Service Pack 2

To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Microsoft SQL Server 2000

To resolve this problem, obtain the latest service pack for SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

WORKAROUND

To work around this problem, use System Monitor to collect Performance Monitor counters. For more information about System Monitor, visit the following Microsoft Web site:

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_mpmonperf_02.mspx

Additionally, you may experience the problem that is described in the "Symptoms" section when you use the SQLDiag utility or the PSSDiag utility to monitor several instances of SQL Server at the same time. To work around this problem in this case, monitor a specific instance of SQL Server instead of monitoring several instances of SQL Server at the same time. To do this, follow these steps:
  1. In a text editor such as Notepad, open the configuration file for the utility that you are using. The default configuration file for the PSSDiag utility is either the Pssdiag.ini file or the Pssdiag.xml file. The default configuration file for the SQLDiag utility is the Sqldiag.xml file. The default configuration file is located in the same folder as the utility.
  2. In the configuration file, locate the Instance XML tag.
  3. Change the default instance name from * to the name of the instance of SQL Server that you want to monitor.

    Note When you specify the instance name, you must not include the computer name. For example, if the full instance name is MYSERVER\MYINSTANCE, you will only type name="MYINSTANCE".
  4. Save the changes by using a different configuration file name, and then exit the text editor.
  5. Specify the /I switch for the SQLDiag utility or for the PSSDiag utility, and then pass the name of the configuration file that you saved in step 4. For example, if the configuration file that you save is named MyNewConfigFile.xml, and the file is located at C:\, you can run the SQLDiag utility by using the following command at the command line:

    sqldiag.exe /i c:\mynewconfigfile.xml

    Or you can run the PSSDiag utility by using the following command:

    pssdiag.exe /i c:\mynewconfigfile.xml

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, 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

Modification Type:MinorLast Reviewed:8/16/2006
Keywords:kbsql2005tool kbDiagnostics kbExpertiseAdvanced kbtshoot kbprb KB906532 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.