Installing Reporting Services 2005 on Named Instance

/0 Comments/in /by

Here are the steps I’ve recently followed to install successfully SRRS 2005 on a named instance.




  1. Follow the steps in the “To Install Reporting Services Side-by-Side With an Earlier Version” section in BOL.


  2. Navigate to http://localhost/reportserver/. If you get access denied error to rsreportserver.config (or another folder/fiile), add the SSRS Windows Services account (e.g. NT AUTHORITY\SYSTEM) and the Web service (ASPNET) to the SQLServer2005ReportServerUser$<machine>$<instance> and  SQLServer2005ReportingServicesWebServiceUser$<machine>$<instance> Windows groups respectively.


  3. Try to open Report Manager. If you get an error that the Report Server cannot open a connection to the database, go back to the Reporting Services Configuration tool.



  • Switch to the Database Setup tab.


  • Select the Server Name and Database Name (ReportServer) and click the Script button.


  • In the Create Scripts dialog, select the Grant Rights Script option.
    Type in the Web service account (e.g. ASPNET) in the User Name field and select the Windows User Account checkbox. Click OK to generate the script.


  • Double-click the script file to open it in the SQL Server Management Studio and execute it. This should grant the necessary permissions to the Web service to connect.

Strangely, on a Windows 2000 box, the Reporting Configuration Tool was showing the following error:


ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070005   at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)


I wasn’t able to figure out how to fix the above error message but it didn’t seem to affect the Report Server.