This hotfix also applies to Microsoft SQL Server 2012 Reporting Services (SSRS 2012) and SQL Server 2014 Reporting Services (SSRS 2014).
Consider the following scenario:
You install an instance of Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2), SQL Server 2012 Reporting Services (SSRS 2012), or SQL Server 2014 Reporting Services (SSRS 2014) on a computer that is running Windows Server 2003, 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 Reporting Services remotely.
In this scenario, the Remote Registry service crashes on the computer that has SQL Server Reporting Services installed. Additionally, error messages that resemble the following are logged in the Application log on the computer that has the instance of SQL Server Reporting Services installed:
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,Error,ServerName,7034,Service Control Manager,N/A,N/A,"The Remote Registry service terminated unexpectedly. It has done this number time(s)."
This issue occurs because the SQL Server Reporting Services Performance Counter uses an incorrect method to call the RegQueryValueEx API to access a registry key. This behavior causes the Remote Registry service to crash.
Note The Remote Registry service loads the SQL Server Reporting Services Performance Counter.
Cumulative update information
The issue was first fixed in the following cumulative update of SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server: