How to: Troubleshoot a Reporting Services Installation Problem
The setup process for SQL Server 2005 Reporting Services supports two modes of installation: install a Reporting Services instance in the default configuration, or install a files-only installation that copies program files to disk. If you are encountering installation problems, consider using a files-only installation. Later, when you configure the report server for operation, you can adjust computer settings or the run time environment to support report server operations. If you are encountering installation problems with a files-only installation, use the information in this topic to resolve the problem.
Verify prerequisites
Internet Information Services (IIS) 5.0 or later must be installed.
The IWAM_computername account must not be configured as a roaming profile.
MDAC 2.6 or later must be installed.
Distributed Transaction Coordinator (DTC) must be started.
ASP.NET must be registered with Internet Information Services
Run aspnet_regiis -i from the %windir%\Microsoft.Net\Framework\v2.0.50727 folder.
Run iisreset to restart IIS.
Check the Setup log files
- View the log files created by Setup. For more information, see How to: View SQL Server 2005 Setup Log Files.
Verify all services are running and features are enabled
Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, click SQL Server Surface Area Configuration.
In Surface Area Configuration for Services and Connections, verify that the Report Server Windows service is running. If the report server database is hosted on the local Database Engine instance, verify that the SQL Server (MSSQLSERVER) is also running.
In Surface Area Configuration for Features, verify that Scheduled Events and Report Delivery is enabled. Verify that HTTP and Web Service Requests is enabled. Verify that Windows Integrated Security is enabled.
See Also
Tasks
Concepts
Installing SQL Server Reporting Services
Other Resources
Troubleshooting Reporting Services