Before you begin installing components, be sure to do the following:

• Review the introduction to deployment configurations so that you are familiar with the components that you are about to install. For more information, click Deployment Configurations for Reporting Services in SharePoint Integrated Mode.
  
• Review the configuration overview topic for best practice recommendations on service account configuration and to learn more about the configuration steps. For more information, click Configuring Reporting Services for SharePoint 3.0 Integration.
  
• Review the hardware and software requirements that apply to all deployment scenarios that include Reporting Services in SharePoint integrated mode. For more information, click Requirements for Running Reporting Services in SharePoint Integrated Mode.
  
• Review the remaining items in this section to learn about additional requirements that apply to a standalone server configuration.
  

Server Requirements for a Multi-server Deployment

You must have at least two or three servers. Hosting the application databases on a third server used exclusively by the Database Engine is common technique for improving performance if you anticipate a relatively large number of users.

If you are using two servers, each one should have the following components:

• On one server, install SQL Server 2005 Server Pack 2 (SP2) Reporting Services and Database Engine. This server will be used to host the report server as well as the report server database and SharePoint application databases.
  
• On the second server, install the Microsoft .NET Framework 3.0 redistributable package, an instance of a SharePoint product or technology, and the Reporting Services Add-in. This server will be the primary server in the farm. Central Administration will be installed on this server. Users will access report server content from the site collection on this computer.
  

Account Requirements for a Multi-server Deployment

You must have a domain user account to connect the instance of the SharePoint product or technology to the SharePoint_config database. Server farms require that you use domain accounts for services and database connections. If possible, create a new account that can be used for just this application. Avoid using your own credentials or those of any user who will be accessing a SharePoint site as a regular user (you will get access denied errors).

You must create a SQL Server database login for the domain account. The login needs DBCreator permissions on the server.

You must configure the SharePoint application pool process account to run as a domain user.

You must configure the Report Server Web service and Windows service to run as domain user accounts.

Important:

For distributed server deployments where the report server, the SharePoint Web application, and the server databases are on three different computers, you can use default settings that include the default Web site and port assignments. If you install the SharePoint Web application and the report server on different computers, but you put the SharePoint databases on the report server computer, you will encounter connection errors unless you follow the guidelines about service account configuration described in the previous section. For more information, see How to: Configure Service Accounts (Reporting Services Configuration).

Administrator credentials are required to run all Setup programs, to grant permissions to be the primary site collection administration, and to grant database access when configuring report server integration.

Internet Information Services (IIS) Requirements for a Multi-server Deployment

Because the report server and the SharePoint application are on different IIS Web servers, you can use the default Web site and port 80 on each computer to access each server application. To minimize steps, the instructions assume you are using the default Web sites and port 80 for each, but you can use different ports and sites if you prefer.

You can install the component technologies in any order, but for best results you should install Reporting Services first and verify that you have a valid installation before you install the SharePoint product or technology.

The following list provides a summary of the deployment tasks:

1. Install Reporting Services and Database Services. If you are installing server software on a production server or if you are using a three-server deployment configuration, plan on choosing the Install but do not configure the server option so that you can control when and how the report server is configured.
   
2. Configure the report server, and verify you have a valid installation.
   
3. Apply SQL Server 2005 SP2.
   
4. Download and install the .NET Framework 3.0 redistributable package.
   
5. Install Windows SharePoint Services or Office SharePoint Server 2007. Plan on choosing the Advanced installation option so that you can specify a remote database server during configuration.
   
6. Run the SharePoint Products and Technologies Configuration Wizard and select the database server.
   
7. Configure the site collection features in Central Administration and open the SharePoint site to verify you have a valid installation.
   
8. Download and install the Reporting Services Add-in for SharePoint Technologies.
   
9. Configure the report server integration features in Central Administration.
   

• Install Reporting Services and the Database Engine on the same computer or on different computers. For more information, see How to: Install a Local Report Server and Remote Report Server Database.

After Setup is finished, configure the report server for native mode operation to verify that the installation succeeded. Doing so allows you to use Report Manager to verify the installation.

For instructions on how to start the Reporting Services Configuration tool and configure the report server for operation, see Reporting Services Configuration How-to Topics.

• Download and install SQL Server 2005 SP2. For more information, see How to obtain the latest SQL Server 2005 Service Pack on the Microsoft Web site.

  Apply SP2 to both Reporting Services and the instance of the Database Engine. If you install the Database Engine and Reporting Services on separate computers, be sure to apply SP2 to both installations.

1. On a different server that you will use for the instance of the SharePoint product or technology, download the .NET Framework 3.0 redistributable package from the Microsoft Download Center.

2. Run Setup. Setup runs in the background and might take a while to complete. To check its progress, click the Microsoft .NET Framework 3.0 Installation icon in the notification area of the taskbar.

1. Run Setup.exe from the installation media for Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server.

2. Enter the 25-character product key.

3. Accept the software license agreement.

4. Click Advanced.

   1. On Server Type, click Web Front End
      
   2. The Data Location tab specifies file location for search index files. On Data Location, use the default value or choose a computer that has excess disk space.
      
   3. Click Install Now.
      

5. Configure the SharePoint product or technology. The SharePoint Product and Technology Configuration Wizard should start after Setup is finished. If it does not, start it from Administrative Tools.

   1. Click Next on the Welcome screen.
      
   2. Click Yes to restart the services if required.
      
   3. On the Connect to a Server Farm page, click No, I want to create a new server farm, and then click Next.
      
   4. On the Specify Configuration Database Settings page, enter the database server name. If you installed the database engine as a default instance, the database server name is the computer name.
      
   5. In User Name and Password, type the credentials of a domain user account that has permission to log on to the computer, a SQL Server database login, and DBCreator permissions on the server. If possible, specify an account that is used only to run this application. Do not type the credentials of a user who will later access the SharePoint site; otherwise, that user might receive access denied errors later when accessing content on the site. Click Next.
      
   6. On the Configure SharePoint Central Administration page, click Next to accept all of the defaults. If you know that impersonation and delegation features are enabled for Windows Authentication in your domain, you can select Negotiate (Kerberos) instead. Otherwise, choose the default value and click Next.
      
   7. On Completing the SharePoint Products and Technologies Configuration Wizard, click Next to start the configuration using the settings you specified.
      
   8. Click Finish.
      

1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration. Follow the checklist in the Administrator's Tasks. For more information about each task, click the link Read the deployment steps and then open the Quick Start Guide. The tasks in the following steps are required.

2. Create a Web application:

   1. Click Create SharePoint Sites.
      
   2. Click Create new Web application.
      
   3. Select Create a new IIS web site (SharePoint - 80) using the default values. This includes using port 80, no host headers, default path, NTLM, and no Anonymous access. Be sure to specify the application pool process account. Choose a domain user account.
      
   4. Click OK.
      

3. Click Create Site Collection on the Application Created page.

   1. Enter a title.
      
   2. Use all default values. When specifying Primary Site Collection Administrator, specify an account that has local administrator permissions.
      
   3. Click OK.
      

4. Open a command prompt window and type iisrest /noforce.

5. Click the URL to verify the site.

6. (Optional) In Central Administration, enable diagnostic logging.

1. Install and configure the Windows SharePoint Services object model on the report server computer. For instructions, see How to: Install a SharePoint Web Front-End on a Report Server Computer.

   1. A browser window will open to Central Administration on the primary server, allowing you to verify that the server farm configuration succeeded.
      

2. Configure the report server for integration:

   1. Start the Reporting Services Configuration tool and connect to the report server instance. For instructions, see How to: Start Reporting Services Configuration.
      
   2. In the navigation pane, click Windows Service Identity. Verify that it is using a domain user account. If it is not, configure it to use one.
      
   3. In the navigation pane, click Web Service Identity.
      
   4. For Report Server, click New.
      
   5. In New Application Pool, enter a name.
      
   6. Click Windows Account.
      
   7. Enter a domain user account.
      
   8. Click OK.
      
   9. Click Apply.
      
   10. In the navigation pane, click Database Setup.
       

       Note:
       If you are using a remote Database Engine instance, see How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration) for more information.

   11. In Server Mode, click Change.
       
   12. Click Yes to confirm that you want to create a new report server database that supports SharePoint integrated mode operations.
       
   13. In Database Name, type a name for the new database (for example, reportserverSharepointMode).
       
   14. Verify that the check box Create a report server database in SharePoint integrated mode is selected.
       
   15. Click OK to create the database.
       
   16. Click Apply to automatically configure the remaining connection settings. You will be prompted to connect to the instance of the Database Engine to complete this step. Click OK to confirm the connection.
       
   17. Configure the unattended execution account and any other settings you want to change. The values for the Report Server virtual directory should still be valid. However, Report Manager will no longer be accessible now that you have configured the report server to use a SharePoint integrated mode database (the tab for the Report Manager virtual directory should be grayed out).
       

1. Click Microsoft SQL Server 2005 Reporting Services Add-in for SharePoint Technologies to go to the download page on the Microsoft Web site.

   Important:
   You must be a SharePoint Web farm administrator and Site Collection Administrator to install the Reporting Services Add-in.

2. Choose which language to install.

3. In Files to Download, click Download to install either the 32-bit or 64-bit version of the Reporting Services Add-in.

4. Click Save to save the file to a location on your computer.

5. Open Windows Explorer and browse to the folder where the file is located.

6. Double-click SharePointRS.msi to begin installation. For instructions, see How to: Install the Reporting Services Add-in.

7. Get the latest version of the readme file for the Reporting Services Add-in to review late-breaking changes and known issues. On the download page on the Microsoft Web site, in Files to Download, click Download to open the readme_rsaddin.htm file, and then save the file to your computer.

1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

   Important:
   To complete the steps below, you must be a member of the SharePoint Farm Administrator group and a Site Collection administrator.

2. Click Application Management. You should see a new section named Reporting Services. This section has links to pages used to specify integration settings. If you do not see this section, you must activate the report server integration feature. For more information, see How to: Activate the Report Server Feature in SharePoint Central Administration.

   At a minimum, you must set the report server URL, select an authentication mode, and grant report server access to the SharePoint databases. For more information, see How to: Configure the Report Server Integration Feature in SharePoint Central Administration.

3. Close Central Administration.

You will get an error if the Reporting Services services are running under built-in accounts. If you already configured the services to use domain user accounts, reset IIS and the Report Server Windows service to clear out old connection information (assuming there are existing connections in the current session). For more information about service account configuration, see Configuring Service Accounts and Passwords in Reporting Services.

Verify integration by starting the Reporting Services Configuration tool and opening the SharePoint Integration page to view server status. You should see a link that you can click to start SharePoint Central Administration.

You can also verify an installation by opening a browser window to the report server. The URL should be similar to http://example-server-name:8080/reportserver. This URL is to the proxy endpoint. After you add report server items to a SharePoint library, you can open a browser window to this URL to view items on the site.

Finally, you should be able to open the SharePoint Web application and upload reports and other documents to a SharePoint library.

After you install all of the components and configure the settings for connecting server components, you must assign permissions, add content types, and add report server items to a SharePoint library.

To finish the deployment tasks for server integration:

1. Open the SharePoint Web application. By default, the URL is http://<your-server-name>.
   
2. Set permissions to grant user access to the SharePoint site. Security is required, but if you want to inherit existing permissions, you do not have to set permissions on specific items. For more information, see Managing Permissions and Security for Report Server Items on a SharePoint Site or How to: Set Permissions for Report Server Items on a SharePoint Site.
   
3. Add Reporting Services content types if you want to create new shared data sources, report models, and Report Builder reports. For more information, see How to: Add Report Server Content Types to a Library (SharePoint Integrated Mode).
   
4. Create shared data sources to use with reports and models. For more information, see How to: Create and Manage Shared Data Sources (SharePoint Integrated Mode).
   
5. Create shared schedules to use with subscriptions or unattended report processing. For more information, see How to: Create and Manage Shared Schedules (SharePoint Integrated Mode).
   
6. Publish report definition files (.rdl), data source files (.rds), and report model files (.smdl) to a SharePoint library. You can also use the Upload command in a SharePoint library to upload .rdl and .smdl files, but not .rds files. Depending on your permissions, you can also create reports in Report Builder and save them to a library. If the reports include references to shared data sources or external files, you must update the references. For more information, see Deploying Reports, Models, and Shared Data Sources to a SharePoint Site and How to: Upload Documents to a SharePoint Library (SharePoint Integrated Mode).
   

When you upload reports, make sure that the data source properties for the report are correct. The data source must have a valid connection string to an external data source. The credential type must be valid for your network topology. Specifically, if Kerberos authentication is not enabled for your domain, you cannot use the Windows integrated security credential type. Instead, you should specify stored credentials. After you verify the data source properties are correct, you can click the report name to open the report. The report will open in the Report Viewer Web Part automatically.

If the report does not open, check permissions on the report and the data source properties that define a connection to the external data source. On a site or farm, SharePoint permissions are used to control access to reports, report models, shared data sources, and the Report Builder tool used to create ad hoc reports. If these items are not visible to users, you should verify that permissions are set correctly.

A report server that runs in SharePoint integrated mode cannot be managed through Report Manager or SQL Server Management Studio. For a complete list of supported and unsupported features, see Features Supported by Reporting Services in SharePoint Integration Mode.

Tasks

Concepts

Other Resources

Help and Information