THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

The Rambling DBA: Jonathan Kehayias

The random ramblings and rantings of frazzled SQL Server DBA

Setup Failure: Performance Counter Last Value Check (SQL Server 2005)

I happened to have the need to go back after the fact and add Integration Services to a Server.  The server has been in production use for almost two years now and one of our new applications needed an Integration Services package to load data from Active Directory into some tables.  No problem, I can install SSIS onto the server and I can also apply the latest service pack to it without forcing a reboot of the server, or can I?

Well I happened to get the following error during the System Configuration Check:

Performance Monitor Counter Requirement (Error)

The System Configuration Check for Performance Monitor counter registry value has failed. For details, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005, in the readme file or in SQL Server Books Online.

So off to Google, and a quick search brings me to the the Books Online page that describes this problem:

How to: Increment the Counter Registry Key for Setup in SQL Server 2005 

Basically the problem is that the "Last Help" DWORD value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib registry key doesn't match the highest number stored in the "Help" DWORD value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 registry key.

Or, the problem is that the "Last Counter" DWORD value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib registry key doesn't match the highest number stored in the "Counter" DWORD value in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009 registry key.

To view this information open the registry editor with regedit or regedit32, and navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib registry key.  The image below highlights the two DWORDs that are being referenced.

image

To find the mismatched values, click on the 009 Key, and then double click on the Counter Multi-String value and scroll to the bottom.  The last number should match the number on the DWORD in the previous image.

image

In this case the both match because the problem does not exist, but if they are different, make note of the last value in the Multi-String entry.  Also check the Help Multi-String values as well and note the last number in the value if it is different.

image

To fix the problem, double click on the appropriate DWORD under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib registry key and then change the Base to Decimal.  Then type in the previously noted value from the Multi-String value in the 009 key that matches to edited DWORD name.

image

Click Ok to save it and then rerun setup.  The check will now pass and you can continue with your installation.

Published Monday, February 09, 2009 1:42 PM by Jonathan Kehayias
Filed under:

Comments

 

Tom said:

Thanks for this. Just used the process to resolve the same issue.

April 22, 2009 7:48 AM
 

wing said:

You are a lifesaver !

July 21, 2009 11:16 AM
 

Rajesh said:

Hi

Thanks a Ton..........u saved my time.......

September 1, 2009 4:59 PM
 

dier said:

thanks dude...

November 5, 2009 3:43 AM
 

Mike said:

Worked like a charm. Thank you for a clear set of instructions !

October 14, 2010 10:25 AM
Anonymous comments are disabled

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement