Deploying Reporting Services and Windows SharePoint Services Side-by-Side
You can run a report server and Microsoft Windows SharePoint Services together on a single Microsoft Internet Information Services (IIS) 6.0 server as long as each service runs in a different application pool and the Reporting Services virtual directories are added to the Windows SharePoint Services list of exclusions.
You can run the servers as separate standalone servers, or you can integrate the servers if you want to store and manage report server items in SharePoint content databases. This topic provides instructions for running servers in standalone mode, side-by-side on the same computer. For more information about how to configure a side-by-side installation that runs in SharePoint integrated mode, see Configuring Reporting Services for SharePoint 3.0 Integration.
You can install Reporting Services and Windows SharePoint Services in any order. The installation order determines whether side-by-side deployment is handled automatically or requires additional configuration.
If you install SharePoint Services first, the Reporting Services virtual directories will be added to the SharePoint list of exclusions automatically when you install or configure Reporting Services. Both the SQL Server Setup program and the Reporting Services Configuration tool are able to detect an existing SharePoint Services installation and modify the list of exclusions accordingly.
If you install SharePoint Services after Reporting Services is already installed and configured, your Reporting Services installation will be unusable until you perform the following steps:
- Start the Reporting Services Configuration tool.
- Configure the Report Server virtual directories.
When you configure the virtual directories, the Reporting Services Configuration tool adds them to the SharePoint list of exclusions. Note that a Report Server application pool is created by default for the Reporting Services virtual directories. Using a dedicated application pool can help avoid conflict with existing Web applications.
Windows SharePoint Services can be downloaded from the Microsoft Download site at www.microsoft.com. The executable that installs the service is Stsv2.exe. To install Windows SharePoint Services, choose a computer that is running Windows Server 2003 with IIS 6.0 in Worker Process Isolation Mode and ASP.NET enabled.
Troubleshooting Steps for Side-by-Side Deployment
If you are encountering problems in your side-by-side installation, you can try the following steps to resolve the issues:
- Run the following commands to add the Reporting Services virtual directories to the Windows SharePoint Services list of exclusions. If you installed Reporting Services using the default virtual directories, run the following at the command prompt (be sure to replace localhost with the Web server name if you are using a different Web host):
STSADM.EXE -o addpath -url http://localhost/ReportServer -type exclusion
STSADM.EXE -o addpath -url http://localhost/Reports -type exclusion
By default, the Stsadm.exe file is located in C:\Program Files\Common Files\Microsoft Shared\Web server extensions\60\bin.
- Run the Reporting Services Configuration tool. If you have not yet configured the report server for operation, you must create the report server and Report Manager virtual directories, specify service accounts, and create the report server database. For more information about how to set the options in the tool, see Reporting Services Configuration F1 Help.
If you configured the report server before installing Windows SharePoint Services, check the application pool settings for the Web service to verify they are correct:
- Open the Web Service Identity page.
- Verify that the application pool for the report server and Report Manager is set to ReportServer application pool (or another application pool that you defined for the service). The application pool used by the report server must be different from the one used by SharePoint Services.
In the previous release, the documentation recommended that you enable session state. Enabling session state is no longer a requirement. However, if you do not enable session state, session state for Report Manager folder pages that are set in Detail view will not be preserved. If you require session state for Detail view, enable session state by setting enableSessionState to true in the SharePoint Web.config file located at C:\Inetpub\wwwroot.
Comparing Levels of Integration Across Versions of Reporting Services and SharePoint Technologies
Reporting Services and SharePoint Technology Integration
Deployment Modes for Reporting Services
Viewing Reports with SharePoint 2.0 Web Parts
Configuring Reporting Services Components