Article ID: 2159286 - Last Review: December 19, 2011 - Revision: 14.0

FIX: The Remote Registry service crashes when an application tries to retrieve performance counter data from an instance of SQL Server on another computer

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Microsoft distributes Microsoft SQL Server 2005, Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005, Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2 fix release

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You install an instance of Microsoft SQL Server on a computer that is running Windows Server 2005 or Windows Server 2008, Windows Vista, or a later version of Windows.
  • You run an application on another computer. The application tries to retrieve the Performance Counter data for the instance of SQL Server remotely.
In this scenario, the Remote Registry service crashes on the computer that has SQL Server installed. Additionally, error messages that resemble the following are logged in the Application log on the computer that has the instance of SQL Server installed:
Faulting application name: svchost.exe_RemoteRegistry, version: 6. .7600. 6385, time stamp: 0x4a5bc3c
Faulting module name: perf-MSSQLSERVER-sqlctr 0. .275_unloaded, version: 0.0.0.0, time stamp: 0x4b48 09 Exception code: 0xc0000005
Fault offset: 0x00000000626bfe57
Faulting process id: 0x d 8
Faulting application start time: 0x0 cad723f5bfd536
Faulting application path: Drive:\Windows\system32\svchost.exe
Faulting module path: perf-MSSQLSERVER-sqlctr 0. .275
Report Id: da45823c-4327- df-ad 9-00 7a477845a

Faulting application name: svchost.exe_RemoteRegistry, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sqlctr90.dll_unloaded, version: 0.0.0.0, time stamp: 0x492b1b55
Exception code: 0xc0000005
Fault offset: 0x000000003353c171
Faulting process id: 0x2eec
Faulting application start time: 0x01cad5a366dde911
Faulting application path: Drive:\Windows\system32\svchost.exe
Faulting module path: sqlctr90.dll
Report Id: d0a6f0d5-41b3-11df-ae47-0017a4778006

Additionally, an error message that resembles the following is logged in the Windows System log on the computer that has the instance of SQL Server installed:
Date,Time PM,Error,ServerName,7034,Service Control Manager,N/A,N/A,"The Remote Registry service terminated unexpectedly. It has done this number time(s)."

Back to the top

CAUSE

This issue occurs because the SQL Server Performance Counter uses an incorrect method to call the RegQueryValueEx API to access a registry key. This behavior causes the Remote Registry service that loads the SQL Server Performance Counter to crash.

Back to the top

RESOLUTION

Note To resolve this issue in SQL Server 2005 Service Pack 3 (SP3), apply Cumulative Update 13 for SQL Server 2005 SP3 on the computer where you have the SQL Server 2005 instance installed. Currently, this resolution only applies to SQL Server 2005 SP3.
Back to the top

Cumulative update information

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2633146  (http://support.microsoft.com/kb/2633146/ ) Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616  (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2567713  (http://support.microsoft.com/kb/2567713/ ) Cumulative Update package 9 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356  (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180  (http://support.microsoft.com/kb/2527180/LN/ ) Cumulative update package 4 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659  (http://support.microsoft.com/kb/2402659/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top


SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2438344  (http://support.microsoft.com/kb/2438344/LN/ ) Cumulative update package 13 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598  (http://support.microsoft.com/kb/960598/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 4

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489409  (http://support.microsoft.com/kb/2489409/LN/ ) Cumulative update package 2 for SQL Server 2005 Service Pack 4
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2485757  (http://support.microsoft.com/kb/2485757/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497673  (http://support.microsoft.com/kb/2497673/LN/ ) Cumulative update package 13 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top

WORKAROUND

We have determined that this problem occurs only when you start Performance Monitoring tools (for example, Windows System Monitor or Logman) remotely and try to connect to a Windows 2008 R2-based server that has SQL Server instances installed. Therefore, we recommend that you do not use Performance Monitoring tools that are installed on a Windows 2003-based server to monitor performance counters that are installed on a Windows 2008 R2-based server. However, if you must use this monitoring environment, make sure that the first connection is made from another Windows 2008 R2-based server. If you do this, all subsequent connections from Windows Server 2003 client computers will be successful.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top
APPLIES TO
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Service Pack 2
  • Microsoft SQL Server 2005 Service Pack 3
  • Microsoft SQL Server 2005 Service Pack 4
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
Back to the top
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2159286
Back to the top