How to: Verify a Reporting Services Installation
When you install a report server using the default configuration, Setup installs and deploys the server. You can verify whether Setup deployed the report server by performing a few simple tests. You must be a local administrator to perform these steps. To enable other users to perform testing, you must configure report server access for those users. For more information, see Server Deployment Checklist in SQL Server Books Online.
The Reporting Services tutorials can help you learn important skills very quickly. There is also a tutorial that introduces each tool. It explains how to start the tool and shows you how each tool looks when it first opens. You can use this tutorial to confirm that all of the tools installed correctly. For more information, see Reporting Services Tutorials and Tutorial: Reporting Services Tools in SQL Server Books Online.
To verify that the report server is installed and running
Run the Reporting Services Configuration tool, connect to the report server instance you just installed, and review the status indicator for each setting to verify that it is configured.
Open the Services window and verify that the Report Server Windows service is running. To view the status of the Report Server Windows service, click Start, point to Control Panel, double-click Administrative Tools, and then double-click Services. When the list of services appears, scroll to Report Server (MSSQLSERVER). The status should be Started.
Open a browser and type the report server URL in the address bar. The address consists of the server name and the virtual directory name that you specified for the report server during setup. By default, the report server virtual directory is named ReportServer. You can use the following URL to verify report server installation: http://<computer name>/ReportServer*<instance name>*. The URL will be different if you installed the report server as a named instance. For more information about the URL format, see Configuring Report Server Virtual Directories.
Run reports to test report server operations. For this step, you can install and publish the sample reports if you do not have any reports available. For more information, see AdventureWorks Report Samples in SQL Server Books Online.
To verify that Report Manager is installed and running
Open a browser and type the Report Manager URL in the address bar. The address consists of the server name and the virtual directory name that you specified for the Report Manager during setup. By default, the Report Manager virtual directory is Reports. You can use the following URL to verify Report Manager installation: http://<computer name>/Reports*<instance name>*.
Use Report Manager to create a new folder or upload a file to test whether definitions are passed back to the report server database. If these operations are successful, the connection is functional.
To verify that Report Designer is installed and running
Open Business Intelligence Development Studio, and create a new project based on a Report Server project type. For more information on using the Report Server Project Wizard, see How to: Create a Report Server Project (Report Designer) in SQL Server Books Online.
If you installed report samples, open the sample report project files and publish the reports to a report server. For more information, see Debugging and Publishing Reports in SQL Server Books Online.
Run a script file (.rss) in the script environment to test Web service operations on the specified report server. For more information on running a sample script, see Script Samples (Reporting Services) in SQL Server Books Online.
Troubleshooting HTTP Errors
Troubleshooting Server and Database Connection Problems
Cause and Resolution of Reporting Services Errors
Reporting Services Installation How-to Topics