Preparing to Install
Before you install, review this section for information that can help you avoid errors during Setup. This topic includes hardware recommendations and information about using a remote SQL Server or named instance, and describes the Web server configuration that Setup expects.
Before you run Setup, you should read the following topics. Understanding the requirements and accounts used by Reporting Services can help you make informed decisions before and during Setup:
- Hardware Requirements for Reporting Services
- Software Requirements for Reporting Services
- System and User Accounts Used in Reporting Services Installation
If you anticipate a high-volume of users or report processing, consider using multiple servers to host the Reporting Services components. Report server and Report Manager should run together on a computer that has ASP.NET and Internet Information Services (IIS) 5.0 or later installed. You can scale a report server installation by running multiple report server instances in a Web farm. You cannot have multiple report server instances on a single computer.
The report server database can be installed on a remote SQL Server instance, or in a cluster. Installing the database on a separate, fast computer provides the best performance. The primary factor in improving performance is to speed disk access on the computer hosting the report server database.
You can host a report server on a domain controller. If the domain controller runs on Windows 2003 server, no additional steps are necessary in order for Reporting Services to install and run properly. On Windows 2000 server, Reporting Services installs properly on a domain controller, but is not activated. In this case, you should perform the following tasks to complete the report server installation. You can perform these tasks before or after running Setup. If you perform them after Setup, you must run rsactivate.exe manully.
- Grant Impersonate Privilege to the IWAM_<machine> account. For more information, see the Knowledge Base Article "IWAM Account Is Not Granted the Impersonate Privilege for ASP.NET 1.1 on a Windows 2000 Domain Controller with SP4" (KB 824308).
- Remove the IWAM_<machine> account from the Guest group. Guest users cannot store or maintain encrypted content. For more information, see the Knowledge Base Article "Roaming Profiles Cannot Create Key Containers" (KB 265357).
- Reboot the computer.
- Run rsactivate if you are performing these steps after Setup is complete.
On both Windows 2000 and Windows 2003, if you are using a Windows account to connect to the report server database, the Windows user must be granted the privilege to log on locally to the domain controller on which the report server is running, even if the report server database is on a different computer. Domain users are not granted this permission by default.
Underscore Characters in Computer Names
Avoid using a computer that has an underscore in the computer name. Report server does not persist session state information on computers that have an underscore character in the computer name and that have been patched with Internet Explorer Security Patch MS01-055. The security patch prevents cookies from being set on client computers that have an underscore in their names, breaking the session management features of Reporting Services. Recommended solutions are documented in Microsoft Knowledge Base article 316112.
Choosing a Remote SQL Server Instance
During Setup, you can choose whether to create the report server database on a local or remote SQL Server instance. If you decide to use a remote SQL Server instance, consider carefully which credentials the report server should use to connect to the SQL Server instance. Setup does not automatically filter out credential types that are not valid for this configuration. Generally, you should avoid choosing Service Account credentials if the SQL Server is a remote instance and you are using an account with reduced privileges (such as Network Service) to run the report server. Instead, consider using a SQL Server login account (recommended) or domain user account to make the connection.
- If the remote SQL Server instance runs as Local System, you can use Windows credentials and any valid domain account to connect to the report server database.
- If the remote SQL Server instance runs as a domain user, you must specify that same domain user account for the report server connection.
Another alternative is to use SQL Server authentication to connect to the remote SQL Server. If you use a SQL Server login, it does not matter what account the remote server instance runs under.
To specify these values, use the Report Server Database page of the Setup wizard.
Note Before you run Setup, disable Terminal Services on the computer on which Setup runs. Terminal Services can interfere with a report server connection to a remote SQL Server instance during Setup. Specifically, Setup attempts to access the remote SQL Server instance using a System account. If the logon fails, an unexpected database error occurs. If you configured Windows Server 2003 for the Terminal Services role, you should remove the role until installation is complete.
Choosing a Named Instance
In some cases, Setup will return an error that a local account does not have network access. This error can occur if you install Reporting Services on Windows XP or Windows 2000, and the local SQL Server is a named instance. When checking for a local SQL Server instance, Setup compares the computer name to the instance name. If the names do not match, Setup assumes that the SQL Server instance is not local.
Web Server Configuration
The report server and Report Manager are accessed through virtual directories that are created and configured during setup. How your Web server is configured can have a large effect on your Reporting Services installation.
Default Web Site or Application Pool
If you are using IIS 5.x, Setup defines the virtual directories under the default Web site. If you are using IIS 6.x, Setup uses the default application pool. If the default Web site or application pool is not available, Setup will continue, but your installation will not work once Setup is finished.
IP Address Mapping
Reporting Services requires that the default Web site IP address is mapped to (All Unassigned). To verify this setting, open the Default Web Site Properties dialog box in Internet Information Services. The IP address is specified on the Web Site tab.
If you are running other middle-tier applications, IIS configuration may have been adjusted to run those programs, and some of those adjustments may prevent a report server from running as expected. For example, if you installed Windows SharePoint services, session state is most likely turned off. In contrast, a report server requires that session state be enabled. For more information about running these applications side by side, see Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services.
Enable the IWAM_ Account to Prevent Setup Error 25619
Setup uses IWAM_computername account to configure IIS. Disabling the account results in Setup error code 25619. To avoid this error, enable the account before running Setup.
Install IIS 5.0 or Later
To install IIS on Windows Server 2003, click Add or Remove Programs in Control Panel. In the Add or Remove Programs dialog box, click Add/Remove Windows Components. The Windows Component Wizard appears. In the Windows Components page, select the Application Server check box. Click Next to configure the component. Click Finish to close the wizard.
For all other operating systems, you can install IIS by clicking Add or Remove Programs, and then clicking Add/Remove Windows Components. The Windows Component Wizard appears. In the Windows Components page, select the Internet Information Services (IIS) check box. Click Next to configure the component. Click Finish to close the wizard.
Report Manager is an ASP.NET application. If you are installing Report Manager, you must have ASP.NET installed and configured. Setup requires that version 1.1.4322 of ASP.NET be registered with IIS. If you are installing Reporting Services on Windows Server 2003, ASP.NET must be running as Network Service.
Install and Configure ASP.NET Version 1.1
ASP.NET is required for the Report Server and the Report Manager components. On Windows Server 2003, ASP.NET must run as Network Service (this is the default logon account for ASP.NET).
To enable ASP.NET on Windows Server 2003, you can use Configure Your Server Wizard or Add or Remove Programs. To enable ASP.NET using Configure Your Server Wizard, add the Application Server role to the server. To enable ASP.NET using Add or Remove Programs, click Add/Remove Windows Components. The Windows Component Wizard appears. In the Windows Components page, select the Application Server check box, and click Details. In the Application Server dialog, select the ASP.NET check box. Click OK to return to the Windows Components dialog. Click Next to configure the components. Click Finish to close the wizard.
For all other operating systems, perform the following steps.
- Verify that Microsoft .NET Framework v1.1 is installed. You can confirm that it is installed by searching your disk for the Microsoft.NET\Framework\v1.1.4322 folder. You can also click Add or Remove Programs in Control Panel and confirm that Microsoft .NET Framework 1.1 is shown in the Currently installed programs list.
- Verify that IIS is installed. You can confirm that IIS is installed by clicking Add or Remove Programs, and then clicking Add/Remove Windows Components. The Windows Component Wizard appears. In the Windows Components page, verify that Internet Information Services (IIS) is checked. If not, check it, and click Next to configure the components. Click Finish to close the wizard.
- Run aspnet_regiis -i from the %windir%\Microsoft.Net\Framework\v1.1.4322 folder.
For more information on the ASP.NET mappings, see Microsoft Knowledge Base article 306005: "HOWTO: Repair IIS Mapping After You Remove and Reinstall IIS" at Microsoft Support.