sql server reporting services configuration

8/13/2019 SQL Server Reporting Services Configuration

1/21

SQL Server Reporting Services ConfigurationMarch 28, 2013

Copyright (c) 2010-2013 Hedberg Data Systems, Inc. All rights reserved. This document is forinformational purposes only and should not be construed as a contract or commitment. Neither HedbergData Systems, Inc. nor Steelcase Inc assumes any responsibility for any errors or omissions in thisdocument or any effects thereof.


2/21

2 SQL Server Reporting Services Configuration

Table of Contents

SQL Server Reporting Services Configuration ............................................................................................. 3Audience .................................................................................................................................................... 3Overview .................................................................................................................................................... 3Prerequisites .............................................................................................................................................. 3SSRS Installation Location ........................................................................................................................ 3SSRS Configuration .................................................................................................................................. 4

SSRS Configuration for Windows 2003 ................................................................................................. 5SSRS Configuration for Windows 2008 or Windows 2008 R2 ............................................................ 10

SSRS Database Recovery Model ........................................................................................................... 21


3/21

SQL Server Reporting Services Configuration 3

SQL Server Report ing Serv ices Conf ig urat ion

Audience

This document is intended for the dealers IT person who will be performing the SQL Server ReportingServices 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. SSRSshould have been installed and patched during previous steps. Now we need to configure the SSRSwebsite and databases.

In our experience, SSRS configuration can be difficult to complete when done after the initial SQL Serverinstall. Since most dealers did not install SSRS as part of their initial Hedberg install, we often encounterdiscrepancies between the Microsoft documented configuration procedure and the actual experience. Inaddition, since SSRS came out before Windows 2008 and since Windows 2008 has many added securityfeatures, 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 usedfor 3 main tasks:

Connects two virtual directories to a web site on the Hedberg server:o Reportsan interactive web page used by individuals with permissions to create SSRS

reports.o ReportServerweb 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 storeinformation about reports and data connections along with storing temporary results when renderingreports.

Establishes the appropriate permissions that provide access to the various IIS and SQL serveraccounts and allow the IIS and SQL Server sides of Reporting services to communicate with eachother.

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 Instal lat ion Locat ion

During the configuration of SSRS, you may need to execute a manual step that requires you to know thelocation 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. Undernormal circumstances, Reporting Services is installed in the MSSQL.3 folder but this is not always thecase, 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 anadministrator account.


4/21


2. Open SQL Server Configuration Manager.

Click on SQL Server 2005 Services and highlightthe SQL Server Reporting Services.

Right-mouse click and choose Properties.

3. Click on the Services tab and from the Binary Pathfield, write down the folder where ReportingServices is installed.

You may need to put your cursor in the field to theright of the Binary path prompt and use your arrowkeys to view the rest of the path.

The path will look something like:

C:\Program Files\Microsoft SQLServer\MSSQL.3\Reporting Services

4. Cancel out of the window and exit theConfiguration Manager.

SSRS Conf igu rat ion

Please select the appropriate configuration procedure based on whether your Hedberg server is runningWindows 2003 or Windows 2008 (which includes 2008 R2).

Important note:If you are installing on a Windows 2003 server and encounter problems with theconfiguration, you can use the Windows 2008 procedure steps to complete the installation. Please notethat the Windows 2008 procedure is more complicated and contains many manual steps, includingregistry editing.


5/21


SSRS Conf igurat ion fo r Windows 2003


2. Open Reporting Services Configuration Manager.

When prompted, connect to your SQL instance byclicking on the Connect button.

3. You will notice that some items are marked ingreen and some in red. Unfortunately, because ofbugs in the installation procedure, these are notaccurate!

Start by selecting Report Server Virtual Directory.Youll notice that although it is marked green(complete) it shows as .

Click on the New button to correct.

4. Connect the ReportServer virtual directory to thedefault IIS web site by accepting the default valuesand clicking OK.


6/21


5. Select Report Manager Virtual Directory.

Click on the New button.

6. Connect the Reports virtual directory to the defaultIIS web site by accepting the default values andclicking OK.

7. Select Windows Service Identity.

Make sure that your SQL Server service account isselected.

Enter the service account password and click onApply.

8. Select Web Service Identity.

By default, the IIS application pools use theNetworkService account.

Accept DefaultAppPool by clicking on the Applybutton.


7/21


9. Select Database Connection.

Pull down the Server Name dropdown and selectyour SQL Server instance name.

Click on the Connect button.

10. Accept the default connection information and clickOK 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 creationsand sets appropriate permissions in SQL Server.


8/21


12. Click on the Apply button at the bottom of thewindow. This will execute the report databasecreation and security scripts.

If prompted with a connection dialog, accept thedefault values on the connection dialog box andclick OK.

13. On the main configuration screen, click on theEncryption Keys entry.

Click on Backup and save the encrypted key to afile on a network share. You can use this torecover an SSRS database in case of a disaster.

Click OK to save the file.

14. On the main configuration screen, click on the E-mail settings entry.

Enter your e-mail server information. This is usedfor subscription reports.

Note that the sender address does not have to bea valid e-mail address.

Click the Apply button to save this information.

15. Congratulations! This completes the SSRSconfiguration. We do not use the Executionaccount so you can exit the configuration tool.


9/21


16. Test the web site both locally and remotely byentering the Report Manager (Reports) URL:

http://localhost/Reports

http://Hedberg_server/Reports

Note that the first time you open this virtualdirectory, it can take 30-60 seconds. Subsequentaccess will open almost immediately.

If you get the error TheReportServerVirtualDirectory element is missing, dothe following:

Go to Root:\Program Files\Microsoft SQLServer\MSSQL.3\Reporting Services\ReportManager"and open the RSWebApplication.config file.

Check if the content between theReportServerVirtualDirectory tagsmatches the virtual directory you created for the reportserver. If not, make it match.

ReportServer

FullTrust

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 modelon the SSRS database. Please proceed to theSSRS Database Recovery Modelsection of thisdocument.
http://localhost/Reportshttp://localhost/Reportshttp://hedberg_server/Reportshttp://hedberg_server/Reportshttp://hedberg_server/Reportshttp://localhost/Reports


10/21


SSRS Conf igurat ion for Windows 2008 or Window s 2008 R2

Please note that this configuration section was created from theMicrosoft Knowledgebase Article #938245.


2. Open Reporting Services Configuration Manager.

When prompted, connect to your SQL instance byclicking on the Connect button.

3. You will notice that some items are marked ingreen and some in red. Unfortunately, because ofbugs in the installation procedure, these are notaccurate!

Start by selecting Report Server Virtual Directory.Youll notice that although it is marked green(complete) it shows as .

Click on the New button to correc t.

4. Connect the ReportServer virtual directory to thedefault IIS web site by accepting the default valuesand clicking OK.
http://support.microsoft.com/kb/938245http://support.microsoft.com/kb/938245http://support.microsoft.com/kb/938245http://support.microsoft.com/kb/938245http://support.microsoft.com/kb/938245http://support.microsoft.com/kb/938245


11/21


5. Select Report Manager Virtual Directory.

Click on the New button.

6. Connect the Reports virtual directory to the defaultIIS web site by accepting the default values andclicking OK.

7. Important:You must now exit the configurationtool. Because of Windows 2008 security settingsas well as bugs in the configuration tool, the nextseries of steps that complete the web siteconfiguration are done outside of the tool.

8. Open InetMgr.

Because of security restrictions on Windows 2008,we need to associate the virtual directories createdin the previous steps with an IIS application pool

that uses a domain user.


12/21


9. Navigate down to the Application Pool section.Youll see two existing pools; one regular andone classic.

Choose Add Application Pool

10. Create a pool called Report Server and choose.NET 2.0 and Classic, then click OK.


13/21


11. Right-mouse click on the new pool and chooseAdvanced Settings...

Change the identity to use the SQL serviceaccount 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, selectManage Application, and then Advanced Settings.

13. Pull down the Application Pool drop down andselect the Report Server application pool that youjust created.

Click OK to continue.


14/21


14. Right-click the ReportServer virtual directory,select Manage Application, and then AdvancedSettings.

15. Pull down the Application Pool drop down andselect the Report Server application pool that youjust created.

Click OK to continue.

Exit InetMgr.

16. We now have to manually edit an SSRSconfiguration file.

Using Notepad, open the Rsreportserver.config file

in the SSRS installation path that you noted earlier:

\Program Files\Microsoft SQLServer\MSSQL.x\Reporting Services\ReportServer

replacing x with the number you wrote down.

17. Scroll down to the Service section of theconfiguration file and then find theWebServiceAccount section.

Insert the domain account that you are using foryour SQL service account and Report Serverapplication pool. It should be in the syntax:

domain\username

Save and exit the file.


15/21


18. We need to add the SQL Server service account tothe Reporting Services Web Service User group.

Open Server Manager.

Expand Configuration, expand Local Users andGroups, and then click Groups.

Double-click theSQLServer2005ReportingServicesWebServiceUser $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 tocomplete 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 foryour SSRS installation path.

Note all of the registry keys that will be added ormodified are String values (REG_SZ).


16/21


21. Add or modify a registry key namedApplicationPoolConfigured_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 namedApplicationPoolConfigured_RS.

Set the value to be the name of the applicationpool used in a previous step, Report Server.

23. Add or modify a registry key namedReportManagerIdentityConfigured.

Set the value to be the SQL service account usedin a previous step, using the syntax:

domain\username.

24. Add or modify a registry key namedWebServiceIdentityConfigured.

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 closeRegedit.


17/21


26. We need to restart the Reporting Services servicenow that weve completed the configurationchanges.

Open SQL Server Configuration Manager.

Click on SQL Server 2005 Services and highlightthe SQL Server Reporting Services.

Right-mouse click and choose Restart.

If it fails to restart, review your manualconfiguration steps and correct as needed.

27. Re-open the Reporting Services ConfigurationManager. The two virtual directory steps as wellas the two identity steps should now show asgreen.

If they do not, please review your manualconfiguration steps and correct as needed.

Click on Database setup to continue theconfiguration.

28. Pull down the Server Name dropdown and selectyour SQL Server instance name.

Click on the Connect button.


18/21


29. Accept the default connection information and clickOK 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 creationsand sets appropriate permissions in SQL Server.

31. Click on the Apply button at the bottom of the

window. This will execute the report databasecreation and security scripts.

Accept the default values on the connection dialogbox and click OK.

32. On the main configuration screen, click on the

Encryption Keys entry.

Click on Backup and save the encrypted key to afile on a network share. You can use this torecover an SSRS database in case of a disaster.

Click OK to save the file.


19/21


33. On the main configuration screen, click on the E-mail settings entry.

Enter your e-mail server information. This is usedfor subscription reports.

Note that the sender address does not have to bea valid e-mail address.

Click the Apply button to save this information.

34. Congratulations! This completes the SSRSconfiguration. We do not use the Executionaccount so you can exit the configuration tool.

35. Test the web site both locally and remotely byentering the Report Manager (Reports) URL:

http://localhost/Reports

http://Hedberg_server/Reports

Note that the first time you open this virtualdirectory, it can take 30-60 seconds. Subsequentaccess will open almost immediately.

If you get the error TheReportServerVirtualDirectory element is missing, dothe following:

Go to Root:\Program Files\Microsoft SQLServer\MSSQL.3\Reporting Services\ReportManager"and open the RSWebApplication.config file.

Check if the content between the

ReportServerVirtualDirectory tagsmatches the virtual directory you created for the reportserver. If not, make it match.

ReportServerFullTrust
http://localhost/Reportshttp://localhost/Reportshttp://hedberg_server/Reportshttp://hedberg_server/Reportshttp://hedberg_server/Reportshttp://localhost/Reports


20/21


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 modelon the SSRS database. Please proceed to theSSRS Database Recovery Modelsection of thisdocument.


21/21

SSRS Database Recovery Mod el

1. It is Hedbergs recommendation that you changethe recovery model on the ReportServer databasejust created to Simple Recovery.

This database will change infrequently and can bebacked up using the same maintenance plan usedfor 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 theRecovery Model to Simple.

Click OK to save the changes.

Exit SSMS.

sql server reporting services configuration

Documents