- Installation Pathways and Preparation
- Step by Step: Installing Reporting Services on a Server with IIS
- Installing Reporting Services in a Non-Default Website
- After InstallationTuning and Reconfiguring
- Testing the Installation
- Installing Reporting Services on a Web Farm
- Removing Reporting Services
- Reporting Services Documentation Refresh
- Reporting Services Service Pack 1
- Summary
This chapter is from the book
This chapter is from the book
This chapter is from the book
Testing the Installation
If you installed with SSL enabled, you'll probably find that there is a change you'll need to make to the sample reports Microsoft provides. In most cases, you'll need to correct the project's TargetServerURL to reflect the https:// address of your Report Server.
Let's quickly show you how to use Visual Studio .NET to load, build, and deploy the sample reports. These reports will help verify several aspects of the install and give you a degree of confidence that your installation has succeeded. Let's step through the process:
-
Start Visual Studio .NET on your development system.
-
Open the SampleReports.sln solution file (File |Open |Project. . ). The installation wizard gave you the option of installing the sample reports—we assume you chose to install the report samples. If you changed the path where these were installed, you're on your own, but if you used the default location, you'll find these samples at C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\Reports.
-
Open the Solution Explorer for the SampleReports project, as shown in Figure 2.7.
Figure 2.7 The Solution Explorer Window for SampleReports -
Change the SampleReports TargetServerURL to the URL of your IIS ReportServer virtual directory. To access this property, right-click the SampleReports project in the Solution Explorer and choose Properties. If you're using SSL security, the URL needs to specify https:// instead of http://. Because the IIS ReportServer might not be on the developer's local system—and it's likely not to be—you also need to set the correct server name instead of "localhost."
Figure 2.8 shows how we changed the TargetServerURL to https://betav1/reportserver so that it targets the Betav1 IIS ReportServer virtual directory. This name must match the Common Name you specified in the IIS SSL certificate. Click OK to close the Property page and apply the changes.
Figure 2.8 Change the TargetServerURL to Point to the Correct IIS ReportServer Virtual Directory -
Deploy the SampleReports project, paying close attention to the Output window. To start deployment, right-click on the SampleReports project and choose Deploy. After the Sample Reports project is built, each report definition should deploy one at a time, as shown in Figure 2.9.
Figure 2.9 The Visual Studio .NET Output Window Shows the Deployment Was Successful -
Use a browser to address the TargetServerURL you entered above. Remember, this is the IIS ReportServer virtual directory. For our test, we'll use https://betav1/reportserver. If this works, you should get a page that looks something like Figure 2.10. If you get a Page Not Found error or a permissions error, you have missed a step somewhere or you don't have sufficient rights to see this server.
Figure 2.10 Using a Browser to Address the ReportServer Virtual Directory -
To view one or more of the sample reports, click on the Sample Reports link. This should show a list of the sample reports you just deployed, as shown in Figure 2.11.
Figure 2.11 The betav1/ReportSever SampleReports Directory -
Click on one of the reports in the list to get Reporting Services to render the report. After a window appears that tells you the report is being generated, the selected report should be rendered in the browser. We selected Company Sales, and Figure 2.12 shows how this is rendered in the browser.
Figure 2.12 The Company Sales Report as Rendered in a Browser -
As a final step, you might like to check that the SQL Server Agent is running, in addition to the Report Services Windows service—as they both are used with Report Subscription. We'll tell you more about that in Chapter 4, however, so don't get overly worried about it here.
)
Figure 2.7)
Figure 2.8)
Figure 2.9)
Figure 2.10)
Figure 2.11)
Figure 2.12Once you've completed these steps, you should be ready to continue with the rest of the book with a degree of confidence that you can create, deploy, and view reports in a browser. We'll get into more detail on developing, managing, publishing, and fine-tuning reports in subsequent chapters.