To configure a report server for SharePoint integration, you must have an existing stand-alone report server or a scale-out deployment. You must perform the following tasks on the report server:

1. Create a report server database in SharePoint integrated mode.
   This sets server properties on the report server and activates a new SOAP report server management endpoint that is used for integrated operations. Use the Reporting Services Configuration tool to create the database.
   
2. For deployments that include a SharePoint server farm, install a Windows SharePoint Services Web front-end on the report server computer. The Web front-end joins the report server computer to a SharePoint farm. Installing the Web front-end on the report server computer is only necessary if you deploy the report server and the SharePoint technology instance on separate computers.
   
3. For deployments that include placing the SharePoint databases on the same computer as the report server, configure the Report Server service to run under a domain account. This step is only necessary if the report server and application databases are one computer, and the SharePoint Web application is on another computer.
   

To configure integration on the server running the SharePoint product or technology, you must do the following:

1. Download and install the Reporting Services Add-in for SharePoint Technologies.
   The add-in installs program files and application pages, including pages that you open in Central Administration to set the report server URL and other integration settings. You can specify report server integration settings for a SharePoint farm or a stand-alone SharePoint Web application.
   
2. Activate the report server feature if you did not install the add-in on a root site collection.
   
3. Use SharePoint Central Administration to configure report server integration. Configuration settings include specifying a single report server URL, setting an authentication type on requests directed to the report server, granting database access permissions to the Report Server service account.
   
4. Optionally, in SharePoint Central Administration, you can set report server defaults that enable logging, ad hoc reporting, and limits for report history and time-out values.
   

SharePoint products and technologies can be deployed as a farm or as a stand-alone server. A farm contains one or more virtual servers, where each virtual server is a SharePoint Web application. A report server integrates at the farm level. From the perspective of storage integration, there can only be one report server database for a farm. You can use SharePoint Central Administration to manage integration settings for all the servers in the farm.

Each SharePoint Web application in a farm can be configured to use different authentication providers. This does not affect report server integration in any way. The report server deployment will handle requests for each server in the farm regardless of the authentication provider it uses.

Each Web application has a default top-level site. You can set permissions differently on each top-level site to vary the availability of report server items and operations across all the servers in a farm.

A report server is implemented as a single Windows service that runs under a built-in account or a local or domain Windows user account. In SharePoint integrated mode, the service must connect to the SharePoint content databases with write and execute permissions. Because the service connects to the SharePoint content databases, the account that you use to run the service will have different requirements depending on whether remote connections are used and whether the report server URL proxy endpoint connection uses Windows integrated security or Trusted Account mode.

The following table provides service account recommendations for different deployment scenarios.

Deployment scenario	Services	SharePoint databases	Account recommendation for Report Server service
Single server	All services are installed on the same computer	On same computer	Any (NetworkService, domain user, local user, LocalSystem). Because the applications connect using a local database connection, you can configure the service to run under any account type.
Distributed deployment on multiple computers	SharePoint Web application and the report server installed on separate computers	On a third computer -- Or -- SharePoint server computer	Domain user account -- Or -- NetworkService, but only if you add NT_AUTHORITY\NetworkService to the WSS_WPG Windows group on the report server computer. For more information, see Troubleshooting Configuration Errors.
Distributed deployment on multiple computers	SharePoint Web application and the report server installed on separate computers	On report server computer	Domain user account is required, regardless of how the report server URL proxy endpoint is configured. When SharePoint databases run on a remote computer, the SharePoint Web application explicitly denies database access to the machine accounts of a remote computer. If the report server is on the same computer as the SharePoint databases, and if either service runs under a built-in account, it will be denied access accordingly. Configuring the service to run as domain user account ensures that the report server will not be denied database access because it is running under a prohibited account.

Note:
The report server database is not included in the discussion of service account requirements for database connections. This is because only the report server connects to the report server database.

About SharePoint Service Account Configurations

Service account recommendations for Windows SharePoint Services and Office SharePoint Server state that for a server farm deployment you should run the application pool process as a domain user account, and not as Network Service. Although a domain user account is recommended, it is not required. However, it is important to realize that if you configure a SharePoint Web application to run as Network Service, and the report server is on a remote computer, you will encounter errors when accessing reports and report server features from a SharePoint site if the report server URL proxy endpoint connects in Trusted Account mode. For more information about server errors that occur when you deploy this configuration, see Troubleshooting Configuration Errors.

For more information about the service account connection to a SharePoint technology instance, see Security Overview for Reporting Services in SharePoint Integrated Mode. To read about the service account recommendations for a SharePoint deployment, see Plan for administrative and service accounts in the Windows SharePoint Services product documentation.

Configuring the servers for integrated operations requires multiple tools and steps. Click the following links to read the instructions for configuring server integration in specific deployment scenarios:

• How to: Configure SharePoint Integration on a Stand-alone Server
  
• How to: Configure SharePoint Integration on Multiple Servers
  

Tasks

Reference

Concepts

Other Resources