SQL Server Reporting Services Configuration

SQL Server Reporting Services Configuration March 28, 2013
Copyright (c) 2010-2013 Hedberg Data Systems, Inc. All rights reserved. This document is for informational purposes only and should not be construed as a contract or commitment. Neither Hedberg Data Systems, Inc. nor Steelcase Inc assumes any responsibility for any errors or omissions in this document or any effects thereof.
Table of Contents
SQL Server Reporting Services Configuration ............................................................................................. 3 Audience .................................................................................................................................................... 3 Overview .................................................................................................................................................... 3 Prerequisites .............................................................................................................................................. 3 SSRS Installation Location ........................................................................................................................ 3 SSRS Configuration .................................................................................................................................. 4 SSRS Configuration for Windows 2003 ................................................................................................. 5 SSRS Configuration for Windows 2008 or Windows 2008 R2 ............................................................ 10 SSRS Database Recovery Model ........................................................................................................... 21
SQL Server Reporting Services Configuration

Audience
This document is intended for the dealers IT person who will be performing the SQL Server Reporting Services configuration on their Hedberg server. The person doing the installation will need local Administrator rights on the server.
Overview
SQL Server Reporting Services (SSRS) is used by Hedberg Business Intelligence for reporting. SSRS should have been installed and patched during previous steps. Now we need to configure the SSRS website and databases. In our experience, SSRS configuration can be difficult to complete when done after the initial SQL Server install. Since most dealers did not install SSRS as part of their initial Hedberg install, we often encounter discrepancies between the Microsoft documented configuration procedure and the actual experience. In addition, since SSRS came out before Windows 2008 and since Windows 2008 has many added security features, configuring SSRS on Windows 2008 requires very specialized steps, including editing the registry. SSRS configuration is done through the Reporting Services Configuration Manager tool. This tool is used for 3 main tasks: Connects two virtual directories to a web site on the Hedberg server: o Reports an interactive web page used by individuals with permissions to create SSRS reports. o ReportServer web services used to generate and render reports. This is used both from the Hedberg system and by the Reports web page when creating and displaying reports. Creates a report database along with a reporting temporary database. These databases store information about reports and data connections along with storing temporary results when rendering reports. Establishes the appropriate permissions that provide access to the various IIS and SQL server accounts and allow the IIS and SQL Server sides of Reporting services to communicate with each other.
Prerequisites
This document assumes that you have the following items: Have previously installed SSRS on your Hedberg server. Have the service account name used for your SQL Server services on your Hedberg server.
SSRS Installation Location

During the configuration of SSRS, you may need to execute a manual step that requires you to know the location of your SSRS installation. Each SQL Server component (Database Engine, Analysis Service, Reporting Service) get installed in a subfolder with the name MSSQL.x where x is a number. Under normal circumstances, Reporting Services is installed in the MSSQL.3 folder but this is not always the case, depending on the order of installation and whether you use named instances. This procedure will determine the location for your SSRS installation. 1. Logon to your Hedberg server using an administrator account.
2. Open SQL Server Configuration Manager. Click on SQL Server 2005 Services and highlight the SQL Server Reporting Services. Right-mouse click and choose Properties.
3. Click on the Services tab and from the Binary Path field, write down the folder where Reporting Services is installed. You may need to put your cursor in the field to the right of the Binary path prompt and use your arrow keys to view the rest of the path. The path will look something like: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services
4. Cancel out of the window and exit the Configuration Manager.
SSRS Configuration
Please select the appropriate configuration procedure based on whether your Hedberg server is running Windows 2003 or Windows 2008 (which includes 2008 R2). Important note: If you are installing on a Windows 2003 server and encounter problems with the configuration, you can use the Windows 2008 procedure steps to complete the installation. Please note that the Windows 2008 procedure is more complicated and contains many manual steps, including registry editing.
SSRS Configuration for Windows 2003

1. Logon to your Hedberg server using an administrator account. 2. Open Reporting Services Configuration Manager. When prompted, connect to your SQL instance by clicking on the Connect button.
3. You will notice that some items are marked in green and some in red. Unfortunately, because of bugs in the installation procedure, these are not accurate! Start by selecting Report Server Virtual Directory. Youll notice that although it is marked green (complete) it shows as <not set>. Click on the New button to correct.
4. Connect the ReportServer virtual directory to the default IIS web site by accepting the default values and clicking OK.
5. Select Report Manager Virtual Directory. Click on the New button.
6. Connect the Reports virtual directory to the default IIS web site by accepting the default values and clicking OK.
7. Select Windows Service Identity. Make sure that your SQL Server service account is selected. Enter the service account password and click on Apply.
8. Select Web Service Identity. By default, the IIS application pools use the NetworkService account. Accept DefaultAppPool by clicking on the Apply button.
9. Select Database Connection. Pull down the Server Name dropdown and select your SQL Server instance name. Click on the Connect button.
10. Accept the default connection information and click OK to connect to your SQL Server instance.
11. Click on New... to create the SSRS databases. Accept the default values and click OK. This creates the scripts for the database creations and sets appropriate permissions in SQL Server.
12. Click on the Apply button at the bottom of the window. This will execute the report database creation and security scripts. If prompted with a connection dialog, accept the default values on the connection dialog box and click OK.
13. On the main configuration screen, click on the Encryption Keys entry. Click on Backup and save the encrypted key to a file on a network share. You can use this to recover an SSRS database in case of a disaster. Click OK to save the file.
14. On the main configuration screen, click on the Email settings entry. Enter your e-mail server information. This is used for subscription reports. Note that the sender address does not have to be a valid e-mail address. Click the Apply button to save this information.
15. Congratulations! This completes the SSRS configuration. We do not use the Execution account so you can exit the configuration tool.
16. Test the web site both locally and remotely by entering the Report Manager (Reports) URL: http://localhost/Reports http://Hedberg_server/Reports Note that the first time you open this virtual directory, it can take 30-60 seconds. Subsequent access will open almost immediately.
If you get the error The ReportServerVirtualDirectory element is missing, do the following: Go to Root:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager" and open the RSWebApplication.config file. Check if the content between the ReportServerVirtualDirectory tags matches the virtual directory you created for the report server. If not, make it match. <ReportServerUrl></ReportServerUrl> <ReportServerVirtualDirectory>ReportServer</ReportS erverVirtualDirectory> <ReportBuilderTrustLevel>FullTrust</ReportBuilderTru stLevel> Test the web site locally and remotely, per the screen, above. Now that youve completed the SSRS configuration, we recommend that you change the recovery model on the SSRS database. Please proceed to the SSRS Database Recovery Model section of this document.
SSRS Configuration for Windows 2008 or Windows 2008 R2

Please note that this configuration section was created from the Microsoft Knowledgebase Article # 938245. 1. Logon to your Hedberg server using an administrator account. 2. Open Reporting Services Configuration Manager. When prompted, connect to your SQL instance by clicking on the Connect button.
3. You will notice that some items are marked in green and some in red. Unfortunately, because of bugs in the installation procedure, these are not accurate! Start by selecting Report Server Virtual Directory. Youll notice that although it is marked green (complete) it shows as <not set>. Click on the New button to correct.
4. Connect the ReportServer virtual directory to the default IIS web site by accepting the default values and clicking OK.
10
5. Select Report Manager Virtual Directory. Click on the New button.
6. Connect the Reports virtual directory to the default IIS web site by accepting the default values and clicking OK.
7. Important: You must now exit the configuration tool. Because of Windows 2008 security settings as well as bugs in the configuration tool, the next series of steps that complete the web site configuration are done outside of the tool. 8. Open InetMgr. Because of security restrictions on Windows 2008, we need to associate the virtual directories created in the previous steps with an IIS application pool that uses a domain user.
11
9. Navigate down to the Application Pool section. Youll see two existing pools; one regular and one classic. Choose Add Application Pool
10. Create a pool called Report Server and choose .NET 2.0 and Classic, then click OK.
12
11. Right-mouse click on the new pool and choose Advanced Settings... Change the identity to use the SQL service account name (the syntax is domain\username). Click OK to save the change.
12. Expand Sites then expand the Default Web Site. Right-click the Reports virtual directory, select Manage Application, and then Advanced Settings.
13. Pull down the Application Pool drop down and select the Report Server application pool that you just created. Click OK to continue.
13
14. Right-click the ReportServer virtual directory, select Manage Application, and then Advanced Settings.
15. Pull down the Application Pool drop down and select the Report Server application pool that you just created. Click OK to continue. Exit InetMgr.
16. We now have to manually edit an SSRS configuration file. Using Notepad, open the Rsreportserver.config file in the SSRS installation path that you noted earlier: \Program Files\Microsoft SQL Server\MSSQL.x\Reporting Services\ReportServer replacing x with the number you wrote down. 17. Scroll down to the Service section of the configuration file and then find the WebServiceAccount section. Insert the domain account that you are using for your SQL service account and Report Server application pool. It should be in the syntax: domain\username Save and exit the file.
14
18. We need to add the SQL Server service account to the Reporting Services Web Service User group. Open Server Manager. Expand Configuration, expand Local Users and Groups, and then click Groups. Double-click the SQLServer2005ReportingServicesWebServiceUse r $ComputerName$InstanceName group.
19. Add the SQL Server service account to this group. Click OK to save your changes and exit Server Manager.
20. We now need to add some missing registry keys to complete the web site configuration of SSRS. Open Regedit. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Microsoft SQL Server\MSSQL.x\Setup where x is the same number that you noted for your SSRS installation path. Note all of the registry keys that will be added or modified are String values (REG_SZ).
15
21. Add or modify a registry key named ApplicationPoolConfigured_RM. Set the value to be the name of the application pool used in a previous step, Report Server.
22. Add or modify a registry key named ApplicationPoolConfigured_RS. Set the value to be the name of the application pool used in a previous step, Report Server.
23. Add or modify a registry key named ReportManagerIdentityConfigured. Set the value to be the SQL service account used in a previous step, using the syntax: domain\username.
24. Add or modify a registry key named WebServiceIdentityConfigured. Set the value to be the SQL service account used in a previous step, using the syntax: domain\username.
25. Validate that your entries are correct then close Regedit.
16
26. We need to restart the Reporting Services service now that weve completed the configuration changes. Open SQL Server Configuration Manager. Click on SQL Server 2005 Services and highlight the SQL Server Reporting Services. Right-mouse click and choose Restart. If it fails to restart, review your manual configuration steps and correct as needed.
27. Re-open the Reporting Services Configuration Manager. The two virtual directory steps as well as the two identity steps should now show as green. If they do not, please review your manual configuration steps and correct as needed. Click on Database setup to continue the configuration.
28. Pull down the Server Name dropdown and select your SQL Server instance name. Click on the Connect button.
17
29. Accept the default connection information and click OK to connect to your SQL Server instance.
30. Click on New... to create the SSRS databases. Accept the default values and click OK. This creates the scripts for the database creations and sets appropriate permissions in SQL Server.
31. Click on the Apply button at the bottom of the window. This will execute the report database creation and security scripts. Accept the default values on the connection dialog box and click OK.
32. On the main configuration screen, click on the Encryption Keys entry. Click on Backup and save the encrypted key to a file on a network share. You can use this to recover an SSRS database in case of a disaster. Click OK to save the file.
18
33. On the main configuration screen, click on the Email settings entry. Enter your e-mail server information. This is used for subscription reports. Note that the sender address does not have to be a valid e-mail address. Click the Apply button to save this information.
34. Congratulations! This completes the SSRS configuration. We do not use the Execution account so you can exit the configuration tool. 35. Test the web site both locally and remotely by entering the Report Manager (Reports) URL: http://localhost/Reports http://Hedberg_server/Reports Note that the first time you open this virtual directory, it can take 30-60 seconds. Subsequent access will open almost immediately.
If you get the error The ReportServerVirtualDirectory element is missing, do the following: Go to Root:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager" and open the RSWebApplication.config file. Check if the content between the ReportServerVirtualDirectory tags matches the virtual directory you created for the report server. If not, make it match. <ReportServerUrl></ReportServerUrl> <ReportServerVirtualDirectory>ReportServer</ReportS erverVirtualDirectory> <ReportBuilderTrustLevel>FullTrust</ReportBuilderTru stLevel>
19
Test the web site locally and remotely, per the screen, above.
Now that youve completed the SSRS configuration, we recommend that you change the recovery model on the SSRS database. Please proceed to the SSRS Database Recovery Model section of this document.
20
SSRS Database Recovery Model

1. It is Hedbergs recommendation that you change the recovery model on the ReportServer database just created to Simple Recovery. This database will change infrequently and can be backed up using the same maintenance plan used for your Hedberg_ECAT (i.e. daily full backups). Open SQL Server Management Studio. Highlight the ReportServer database. Right-mouse click and choose Properties.
2. Select the Options section and change the Recovery Model to Simple. Click OK to save the changes. Exit SSMS.
21

SQL Server Reporting Services Configuration

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SQL Server Reporting Services Configuration

Загружено:

Авторское право:

Доступные форматы

SQL Server Reporting Services Configuration March 28, 2013