How to install and how to configure SQL Server 2005 Reporting Services on a computer that is running Windows Server 2008

This article discusses how to install and how to configure Microsoft SQL Server 2005 Reporting Services on a computer that is running Windows Server 2008.

On any edition of Windows Server 2008, you can install one of the following editions of SQL Server 2005 that includes Reporting Services:

• SQL Server 2005 Standard Edition, 32-bit
• SQL Server 2005 Developer Edition, 32-bit
• SQL Server 2005 Enterprise Edition, 32-bit
• SQL Server 2005 Standard Edition, 64-bit
• SQL Server 2005 Developer Edition, 64-bit
• SQL Server 2005 Enterprise Edition, 64-bit
• SQL Server 2005 Workgroup Edition
• SQL Server 2005 Express Edition with Advanced Services Service Pack 3 (SP3) or later service pack.

After you install the release version of SQL Server 2005, you must install SQL Server 2005 Service Pack 3 (SP3) or a later service pack to obtain support from Microsoft.

Note Microsoft SQL Server 2005 Express Edition with Advanced Services SP2 is already at the SQL Server 2005 SP3 level.

Prerequisites

Before you install Reporting Services, you must enable Microsoft ASP.NET and Internet Information Services (IIS). To do this, you must configure a server role.

After you enable the required features, you must start the World Wide Web Publishing service if you want to install the default configuration of Reporting Services. Otherwise, the SQL Server Setup program only installs Reporting Services and does not configure Reporting Services.

For more information about these prerequisites, see "Preinstallation steps" in the "Install SQL Server 2005 Reporting Services SP2" section.

If you are performing an upgrade

If you are performing an upgrade from an earlier version of SQL Server Reporting Services to SQL Server 2005 Reporting Services, you must use the SKUUPGRADE=1 argument if the following conditions are true:

• You use an instance of SQL Server Express Edition to host the report server database.
• You are upgrading from the previously installed edition of Reporting Services and from the previously installed instance of SQL Server Express Edition.

For more information about how to use the SKUUPGRADE=1 argument to upgrade Reporting Services and the instance of SQL Server Express Edition, see the "How to: Upgrade a SQL Server Express report server to other SQL Server editions" topic in SQL Server 2005 Books Online.

For more information about the known issues when you upgrade from one edition of SQL Server 2005 to another edition of SQL Server 2005 SP3, see the readme file of SQL Server 2005 SP3. To obtain the readme file, visit the following Microsoft Web site:

Install SQL Server 2005 Reporting Services SP2

Preinstallation steps

1. Log on to Windows Server 2008.
2. Configure a server role and enable ASP.NET and IIS. To do this, follow these steps:
   1. Click Start, and then click Server Manager.
   2. In Server Manager, right-click Manage Roles, and then click Add roles. The Add Roles Wizard starts.
   3. In the Add Roles Wizard, click Select Server Roles.
   4. On the Select Server Roles page, click to select the Web Server (IIS) check box, and then click Next.
      
      Note Because of role dependency, the File Server check box is automatically selected when you click to select the Web Server (IIS) check box.
   5. On the Role Services page, expand Common HTTP Features, and then click to select the following check boxes:
      • Static Content
      • Default Document
      • Directory Browsing
      • HTTP Errors
      • HTTP Redirection
   6. Expand Application Development, and then click to select the ASP.NET check box.
      
      Note If you are prompted to add required role services, click OK.
   7. Expand Security, and then click to select the Windows Authentication check box.
   8. Expand Management Tools, expand IIS 6 Management Capability, and then click to select the following check boxes:
      • IIS Metabase Compatibility
      • IIS 6 WMI Compatibility
      • IIS 6 Scripting Tools
      • IIS 6 Management Console
   9. Click Next, and then click Install.
   Note If you do not enable all these features, the Reporting Services option does not appear in the Feature Selection dialog box of the SQL Server Setup program.
3. Verify that the World Wide Web Publishing service is started. If the World Wide Web Publishing service is not started, configure the service to start automatically. To do this, follow these steps:
   1. In Control Panel, click System and Maintenance.
   2. Click Administrative Tools.
   3. Double-click Services.
   4. In the User Account Control dialog box, click Continue.
   5. Right-click World Wide Web Publishing Service, and then click Properties.
   6. In the World Wide Web Publishing Service Properties dialog box, select Automatic in the Startup type list.
   7. Click Apply, click Start, and then click OK.

Note If you are installting 32 bit Reporting services in a 64 bit environment, refer to the following Knowledge base article: For more information about how to install a 32-bit version of the reporting services on a 64-bit operating system, click the following article number to view the article in the Microsoft Knowledge Base:

Step 1: Install SQL Server 2005 or SQL Server 2005 Express Edition with Advanced Services SP2

You can install either SQL Server 2005 or SQL Server 2005 Express Edition with Advanced Services SP2. To obtain SQL Server 2005 Express Edition with Advanced Services SP2, visit the following Microsoft Web site: Notes

• When you install the release version of SQL Server 2005, you receive a warning message. The warning message explains that this program has known compatibility issues. Click Run program to continue the installation.
• In the Feature Selection dialog box, make sure that Reporting Services is selected.
• In the Report Server Installation Options dialog box, select one of the following options:
  • Install the default configuration
  • Install but do not configure the server
  Note We recommend that you select the Install the default configuration option. If you select the Install but do not configure the server option, you can manually configure the report server after the installation has finished. However, you may experience problems when you manually configure the report server. For more information about how to resolve these problems, see the "Troubleshoot configuration problems" section.

Step 2: Install SQL Server 2005 SP3

Note SQL Server 2005 Express Edition with Advanced Services SP2 is already at the SQL Server 2005 SP3 level. Therefore, if you previously installed SQL Server 2005 Express Edition with Advanced Services SP2, go to Step 3.

If you previously installed one of the following editions of SQL Server 2005, install SQL Server 2005 SP3:

• SQL Server 2005 Standard Edition, 32-bit
• SQL Server 2005 Developer Edition, 32-bit
• SQL Server 2005 Enterprise Edition, 32-bit
• SQL Server 2005 Standard Edition, 64-bit
• SQL Server 2005 Developer Edition, 64-bit
• SQL Server 2005 Enterprise Edition, 64-bit
• SQL Server 2005 Workgroup Edition

For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: Notes

• You must make sure that the SQL Server service is started before you install SQL Server 2005 SP3. The SQL Server service must be running to perform an authentication check in the Authentication Mode dialog box of the Setup program.
• To avoid a system restart, you can stop the SQL Server service after you close the Authentication Mode dialog box. To stop the SQL Server service, follow these steps:
  1. In Control Panel, click Administrative Tools, and then double-click Services.
  2. In Services, right-click the SQL Server service, and then click Stop.
• If the SQL Server 2005 User Provisioning Tool starts, start the SQL Server service before you grant administrative rights to a user. You can use the SQL Server 2005 User Provisioning Tool to add Windows user accounts to the SYSADMIN fixed server role.

Step 3: Start the SQL Server service and reset IIS

If the SQL Server service is not started, start the service.

Additionally, if you installed SQL Server Express Edition with Advanced Services SP2 in Step 1, you must reset IIS. To do this, follow these steps:

1. Open a Command Prompt window by using the Run as administrator option.
2. At the command prompt, type iisreset, and then press ENTER.

Configure SQL Server 2005 Reporting Services

1. Start the Reporting Services Configuration tool. To do this, click Start, point to All Programs, point to SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.
2. In the User Account Control dialog box, click Continue.
3. In the Report Server Installation Instance Selection dialog box, type the name of the computer in the Machine Name box.
4. Select the instance of SQL Server 2005 Reporting Services in the Instance Name list, and then click Connect.
5. Click Web Service Identity.
6. In the Web Service Identity dialog box, select ReportServer or Classic .NET AppPool in the Report Server list.
7. Select ReportServer or Classic .NET AppPool in the Report Manager list.

How to configure the Report Server Web service or Report Manager to use an application pool that runs under a domain user account

In Windows Server 2008, you must configure the Report Server Web service or Report Manager to use an application pool that runs under a domain user account. To do this, follow these steps:

1. In Internet Information Services (IIS), configure Report Manager to use an application pool that runs under a domain user account. To do this, follow these steps:
   1. Click Start, click Run, type Inetmgr, and then click OK.
   2. In IIS Manager, expand Sites, expand Default Web Site, right-click the Report Manager application, point to Manage Application, and then click Advanced Settings.
      
      Note If you use the default instance of Reporting Services, the name of the Report Manager application is Reports. If you use SQL Server 2005 Express Edition with Advanced Services SP2, the name of the Report Manager application is Reports$sqlexpress. If you use a named instance of Reporting Services, the name of the Report Manager application is Reports$InstanceName.
   3. In the Advanced Settings dialog box, click Application Pool, and then click the ellipsis (�).
   4. In the Select Application Pool dialog box, select the application pool that uses a domain user account, and then click OK.
   5. In the Advanced Settings dialog box, click OK.
2. In IIS, configure the Report Server Web service to use an application pool that runs under a domain user account. To do this, follow these steps:
   1. Click Start, click Run, type Inetmgr, and then click OK.
   2. In IIS Manager, expand Sites, expand Default Web Site, right-click the Report Server Web service application, point to Manage Application, and then click Advanced Settings.
      
      Note If you use the default instance of Reporting Services, the name of the Report Server Web service application is ReportServer. If you use SQL Server 2005 Express Edition with Advanced Services SP2, the name of the Report Server Web service application is ReportServer$sqlexpress. If you use a named instance of Reporting Services, the name of the Report Server Web service application is ReportServer$InstanceName.
   3. In the Advanced Settings dialog box, click Application Pool, and then click the ellipsis (�).
   4. In the Select Application Pool dialog box, select the application pool that uses a domain user account, and then click OK.
   5. In the Advanced Settings dialog box, click OK.
3. Update the Rsreportserver.config file. To do this, follow these steps:
   1. Open the Rsreportserver.config file from the following folder:
      SQLRSInstall\Microsoft SQL Server\MSSQL.X\Reporting Services\ReportServer
      Note SQLInstall represents the location where SQL Server 2005 Reporting Services is installed. MSSQL.X represents the instance ID of SQL Server 2005 Report Services.
   2. Under the Service element, update the WebServiceAccount element to use the domain account.
4. Update the user account in the SQLServer2005ReportingServicesWebServiceUser$ComputerName$InstanceName group. To do this, follow these steps:
   1. Open Server Manager.
   2. In Server Manager, expand Configuration, expand Local Users and Groups, and then click Groups.
   3. Double-click the SQLServer2005ReportingServicesWebServiceUser$ComputerName$InstanceName group.
   4. In the Properties dialog box, add the domain account.
5. Verify that some related registry entries have the correct setting. To do this, follow these steps:
   1. Click Start, click Run, type Regedit, and then click OK.
   2. If you are running a 64-bit version of SQL Server 2005 Reporting Services, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup
      If you are running a 32-bit version of SQL Server 2005 Reporting Services on a 64-bit Windows operating system, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server\MSSQL.X\Setup
   3. Make sure that the ApplicationPoolConfigured_RM registry entry is configured to be the application pool that you selected in step 1d.
   4. Make sure that the ApplicationPoolConfigured_RS registry entry is configured to be the application pool that you selected in step 2d.
   5. Make sure that the ReportManagerIdentityConfigured registry entry is configured to be the domain user account for the application pool that you selected in step 1d.
   6. Make sure that the WebServiceIdentityConfigured registry entry is configured to be the domain user account for the application pool that you selected in step 1d.
      Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.NoteIf any of the registry keys are missing create them as new string values. For example if WebServiceIdentityConfigured registry entry is missing on 64 bit version, use the following procedure to add the same:
      1. Run Registry Editor (Regedt32.exe).
      2. Go to the following key in the registry:
         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup
      3. On the Edit menu, click New String Value and use the following entry:
         Value Name: WebServiceIdentityConfigured
         Data Type: REG_SZ
         String: <domain\user account from Step 1d.>
         :
      NoteRepeat these steps for each keyword that is missing.
6. Restart the SQL Server 2005 Reporting Services service. To do this, follow these steps:
   1. Start SQL Server Configuration Manager.
   2. In SQL Server Configuration Manager, click SQL Server 2005 Services.
   3. Right-click the SQL Server 2005 Reporting Services service, and then click Restart.

Notes

• Reporting Services runs as an earlier application on IIS 7.0. You should avoid running the report server in the default application pool on IIS 7.0. Reporting Services requires that you use an application pool that has the Managed Pipeline Mode option set to Classic. You will receive an "HTTP 500" error message if you run the report server in the default application pool.
• If you select the Install but do not configure the server option when you install Reporting Services, you must configure the options in the following dialog boxes:
  • Report Server Virtual Directory
  • Report Manager Virtual Directory
  • Database Setup
  For more information about how to configure the options in these dialog boxes, visit the following Microsoft Developer Network (MSDN) Web site:
  http://msdn2.microsoft.com/en-us/library/ms159624.aspx

Configure Report Manager and the report server for local administration

1. Click Start, point to All Programs, right-click Internet Explorer, and then click Run as administrator.
2. In the User Account Control dialog box, click Continue.
3. Open Report Manager. By default, the URL of Report Manager is the following:
   http://ServerName/reports
   If you use SQL Server 2005 Express Edition with Advanced Services SP2, the URL of Report Manager is the following:
   http://ServerName/reports$sqlexpress
   If you use a named instance of Reporting Services, the URL of Report Manager is the following:
   http://ServerName/reports$InstanceName
4. Add the URL of Report Manager to the "Local intranet" security zone. To do this, follow these steps:
   1. In Control Panel, double-click Internet Options.
   2. In the Internet Properties dialog box, click the Security tab.
   3. On the Security tab, click Local intranet, and then click Sites.
   4. Under Add this website to the zone, type the URL of Report Manager. If you do not use HTTPS for the default site, click to clear the Require server verification (https:) for all sites in this zone check box.
   5. Click Add.
   6. Under Add this website to the zone, type http://localhost, and then click Add.
      
      Note After you perform step f, you can open a browser window to http://localhost or to the network computer name. Then you can locally manage the report server and Report Manager.
5. Create role assignments that explicitly grant you access together with full permissions. To do this, follow these steps:
   1. Click Start, point to All Programs, right-click Internet Explorer, and then click Run as administrator.
   2. In the User Account Control dialog box, click Continue.
   3. Open Report Manager by using the URL of Report Manager.
   4. On the Home page, click Properties.
   5. Click New Role Assignment.
   6. Type a Windows user account name by using the following format:
      Domain\User
   7. Click to select the Content Manager check box, and then click OK.
   8. On the Home page, click Site Settings.
   9. Click Configure site-wide security.
   10. Click New Role Assignment.
   11. Type a Windows user account by using the following format:
       Domain\User
   12. Click the System Administrator check box, and then click OK.
6. Close Report Manager.
7. Use Internet Explorer with the Run as administrator option to reopen Report Manager.

You should have full permissions to all features of Report Manager. These features include the features that you can access by clicking Site Settings on the Home page.

Troubleshoot configuration problems

Problem 1

Consider the following scenario. You install SQL Server 2005 Express Edition with Advanced Services SP2 on a computer that is running Windows Server 2008 Beta 3. In the Report Server Installation Options dialog box, you select the Install but do not configure the server option. After the installation, you open the Reporting Services Configuration tool. In this scenario, many red icons appear next to the items in Reporting Services Configuration Manager. Additionally, a green icon appears next to Report Server Virtual Directory.

Workaround for Problem 1

To work around this problem, follow these steps:

1. In Reporting Services Configuration Manager, click Report Server Virtual Directory.
   
   Note Although a green icon appears next to Report Server Virtual Directory, the virtual directory for the report server is not created.
2. Click Create.
3. In the Create a New Virtual Directory dialog box, select a Web site in the Website list, and then click OK.
4. Click Apply.
   
   Note You may have to click Apply several times before Reporting Services Configuration Manager creates the virtual directory for the report server.
5. In the Report Manager Virtual Directory dialog box, create a virtual directory for Report Manager.
6. In the Web Service Identity dialog box, select ReportServer or Classic .NET AppPool in the Report Server box.
7. Select ReportServer or Classic .NET AppPool in the Report Manager box.
8. In the Database Setup dialog box, create a report server database.
9. Configure other options depending on your requirements. For more information about how to configure Reporting Services, visit the following MSDN Web site:
   http://msdn2.microsoft.com/en-us/library/ms157412.aspx

Problem 2

When you run a script to configure the virtual directory for the report server, you receive the following error message:

Cause of Problem 2

This problem occurs because of a new permission requirement in IIS 7.0. This permission requirement is for ISAPI extensions that use a wildcard (*) script mapping.

Workaround for Problem 2

To work around this problem, follow these steps:

1. Click Start, click Run, type inetmgr, and then click OK.
2. In Internet Information Services (IIS) Manager, expand Web Sites, expand Default Web Site, and then click the virtual directory for the report server.
3. Under Features View, double-click Handler Mappings.
4. Under Actions, click Edit Feature Permissions.
5. Click to select the Scripts check box, and then click OK.