Troubleshooting Activation Errors
Activation or initialization errors include the following error messages:
- Initialization error 1603
- Failure initializing the Web service
- The service has not generated a public key
The RPC server is not responding
These errors occur when Setup cannot start the Report Server Web service. When the error occurs during Setup, it is because one or more of the following conditions exist (more information about each condition is provided further on in this topic):
- The ReportServer Windows service was not running during Setup.
- Internet Information Services (IIS) configuration for the default Web site includes settings that Setup does not expect.
- ASP.NET 1.1.4322 is not registered with IIS.
- A remote SQL Server instance used to host the report server database does not run as Local System.
- A non-default application pool identity in IIS 6.0 was used for a report server.
- ASP.NET is not running as Network Service on Windows Server 2003.
- IIS 6.0 is running in Compatibility Mode.
To get details about the error, ping the report server to view any errors returned by IIS. You can also view the setup log file (rsmsi*.log) for more information. To do this:
- Open a browser window and type http://localhost/reportserver.
The resulting HTTP message or error code may indicate a permission error, network error, or some other error. In many cases, you can use the information provided to resolve the problem and complete setup.
- On the Start menu, click Run, type %temp%, and click OK. Choose the rsmsi_<timestamp>.log file that was created for the current installation.
Choosing Retry, Cancel, or Ignore
When an initialization error occurs, you can click Retry, Cancel, or Ignore.
Click Retry if you think the issue is related to the ReportServer Windows service not running. First, manually start the ReportServer Windows service:
- In Control Panel, point to Administrative Tools, click Services, and verify Report Server status. If it is not started, right-click Report Server, and click Start on the General tab.
If retrying does not resolve the issue, click Ignore to troubleshoot your installation later.
The following conditions indicate a Windows service issue:
- The error "Failure initializing the Web service: The RPC server is not listening" occurs during the final stages of Setup.
- The error "Initializing Report Service, Error Code 1603" appears on the Setup Error page.
- The error that you see when you navigate to http://localhost/reportserver is "The report server installation is not activated."
Click Cancel if you want more time to investigate your options for resolving the error. Clicking Cancel rolls back Setup. Consider canceling Setup if you are installing a report server on a Web server that hosts other middle-tier applications and you want to avoid disrupting service to those applications. Report server requires that the default Web site be configured to use ASP.NET 1.1.4322. If you have other applications that do not share this requirement, you may want to select a different Web server to host your report server installation.
Click Ignore if you want to continue Setup and initialize the report server, or troubleshoot ASP.NET or IIS configuration issues after Setup is complete. Continuing Setup is recommended if the error occurs because the ReportServer Windows service could not be started during Setup, and clicking Retry did not work.
To initialize the report server, start the ReportServer Windows service, and then run the Rsactivate utility from a command prompt. By default, the path to the configuration file is c:\Program files\Microsoft SQL Server\MSSQL\Reporting Services\Reportserver\RSReportServer.config. If you chose a different install location, you must update the path accordingly. Be sure to restart IIS after you activate the report server. The following syntax initializes a local report server installation:
- From a command prompt, run rsactivate -c"<path to rsreportserver.config>"
To register ASP.NET 1.1.4322
- From a command prompt, run C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
- Give the accounts <computername>\ASPNET and <computername>\Network Service (for Windows Server 2003 systems only) read-write permission to two folders:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files
- Re-run Setup.
- During setup, clear the Use Secure Sockets Layer check box (if you do not have a certificate for your Web server)
Specifying a Remote SQL Server Instance
In this case, the following additional message is appended to the activation error: Unable to connect to the database. In the setup log files, you may also see an entry that describes a logon failure for user (null).
Specifying a Non-default Application Pool Identity in IIS 6.0
When you install Reporting Services on Windows Server 2003, Setup assumes that the Report Server Web service is running as Network Service. If you have configured IIS to use a different identity for the default application pool, Setup fails with error 1603 late in the installation process. An error also occurs if you reconfigure the identity after Reporting Services is installed. In this case, you will get an access denied error ("Access to the path <path>\global.asax is denied.").
The access denied error occurs because the Web service identity is reflected in the credentials used by the Web service to log on to the SQL Server instance that hosts the report server database. The identity value is stored in the rsreportserver.config file as an encrypted value. The value is created during setup, and can only be modified later by running the rsconfig utility. To work around the access denied error, run rsconfig to reset the connection information to the original value, Network Service.
To determine which application pool is used by the report server, open IIS, expand Web Sites, expand Default Web Site, right-click Report Server, and then click Properties to view the value for application pool (the default value configured during setup is DefaultAppPool). To determine the identity that is used by the application pool, open IIS, expand Application Pools, right-click a pool (for example, DefaultAppPool), and then click Properties. Click Identity to view or modify the identity used by the application pool.
ASP.NET Is Not Running as Network Service
Setup error 1603 can also occur when ASP.NET is not running as Network Service, and you use Service Credentials as the credential type for logging on to the SQL Server instance that hosts the report server database. When the error occurs, you can continue Setup, but the report server will not be in working order when Setup is finished.
To activate the report server and complete the installation, you must reset the identity to Network Service and run several command line utilities included with Reporting Services. The command line utilities mentioned in the following steps are all located in C:\Program Files\Microsoft SQL Server\80\Tools\Binn.
- Configure the application pool used by the report server to use Network Service (note that the Report Server Web service requires Network Service in this release).
- Run rskeymgmt with the -d argument to delete all encrypted content. You can type rskeymgmt -? to get help about specific arguments.
- Run rsconfig utility to specify report server connection information (you must specify these arguments: -s, -d, -a, -u, -p). You can type rsconfig -? to get help about specific arguments.
- Restart both IIS and the ReportServer Windows service.
- Run rsactivate utility to activate the server (you must specify these arguments: -c, -u, -p). For argument -c, enclose the path information in quotation marks. You can type rsactivate -? to get more help about specific arguments.
Running IIS 6.0 in Compatibility Mode
This error also occurs when you run IIS 6.0 in IIS 5.0 compatibility mode. In this case, the default account for ASP.NET is <computername>\ASPNET. To change the ASPNET account to Network Service, you must first clear the check box Run WWW service in IIS 5.0 isolation mode (located on the Service tab of the Web Sites Properties dialog). Note that IIS 6.0 automatically runs in compatibility mode when you upgrade a Windows 2000 server to Windows Server 2003.