The following installation will describe the installation and configuration of Reporting Services in SharePoint 2013, what permissions are needed, which accounts to use, where services should be installed based on the SharePoint Farm I am using which contains 2 App, 2 Web, 2 Search and 2 office Web App servers.
Every SharePoint server will need to be installed with both the SQL Reporting Services AND the Reporting Services Add-In to make it work. There is not a lot of information you can find about this and the information you will find most of the times is NOT CORRECT!
PowerPivot for SharePoint 2013 and Reporting Services in SharePoint mode Three Server Deployment
In the following three-server deployment, the SQL Server Database Engine, Analysis Services server running in SharePoint mode, and SharePoint, each run on a separate server. In SQL Server 2012 SP1 the PowerPivot for SharePoint 2013 installer package (spPowerPivot.msi) must be installed on the SharePoint server.
| 1) | Excel Service Application. The service application is created as part of the SharePoint installation. |
| (2) | PowerPivot Service Application. Default name is Default PowerPivot Service Application. |
| (3) | Reporting Services service application. |
| (4) | Install the reporting services add-in for SharePoint from either the SQL Server 2012 SP1 installation media or the SQL Server 2012 SP1 feature pack. |
| (5) | RUN the spPowerPivot.msi to install data providers, the PowerPivot configuration tool, PowerPivot Gallery, and schedule data refresh. |
| (6) | Analysis Services Server in SharePoint Mode. Configure the Excel Services Application Data Model Settings to use this server. |
| (7) | The SharePoint content, configuration, and service application databases. |
Step 1: Install Reporting Services Report Server in SharePoint mode
This step installs a Reporting Services report server in SharePoint mode and the Reporting Services add-in for SharePoint products. Depending on what is already installed on your computer, you may not see some of the installation pages described in the following steps.
- Run the SQL Server Installation Wizard (Setup.exe).
- Click Installation in the left side of the wizard and then click New SQL Server stand-alone installation or add features to an existing installation.
- Click OK on the Setup Support Rules page, assuming all rules passed.
- Click Install on the Setup Support Files page. Depending on what is already installed on your computer, you might see the following message:
- “One or more affected files have operations pending. You must restart your computer after the setup process is completed.”
- Click Ok.
- Click Next after the support files have completed installing and the Support Rules pages show a status of Passed. Review any warnings or blocking issues.
- On the Installation Type page, click Add features to an existing instance of SQL Server 2012. Select the correct instance in the drop-down list and click Next.
- If you see the Product Key page, type your key or accept the default of the ‘Enterprise Evaluation’ edition.
Click Next.
- If you see the License terms page, review and accept the license terms. Microsoft appreciates you clicking to agree to send feature usage data to help improve product features and support.
Click Next.
- If you see the Setup Role page, select SQL Server Feature Installation
Click Next
- Select the following on the Feature Selection page:
- Reporting Services – SharePoint
- Reporting Services add-in for SharePoint Products.
The installation wizard option for installing the add-in is new with the SQL Server 2012 release.
- If you do not already have an instance of SQL Server Database Engine, you could also select Database Engine Services and Management Tools Completefor a complete environment.
Click Next.
- If you see the Installation Rules page. Review any warnings or blocking issues. Then click Next
- If you selected the Database Engine services, accept the default instance of MSSQLSERVER on the Instance Configuration page and click Next.
![clip_image002[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLnY7D51Pf52bb2MMlkVzsEbiEjyoSvQdRYrNUXstEDhJ_LFvXy3W3mwsl5Lx78Wxp8XMxFsS-k9NtWzx9yL7_mNkcISnagUVzdhJMWsgkkLsgCRkYSs3BofoeDzd9t3LpwPw5cwVUK60/?imgmax=800 "clip_image002[1]")
The Reporting Services SharePoint service architecture is not based on a SQL Server "instance" as was the previous Reporting Services architecture.
- Review the Disk Space Requirements page and click Next.
- If you see the Server Configuration page type appropriate credentials. If you want to use the Reporting Services data alerting or subscription features, you need to change the Startup Type for SQL Server Agent to Automatic. You may not see the Server Configuration page, depending on what is already installed on the computer.
Click Next.
- If you selected the Database Engine services, you will see the Database Engine Configuration page, add appropriate accounts to the list of SQL Administrators and click Next.
- On the Reporting Services Configuration page you should see the Install only option is selected. This option installs the report server files, and does not configure the SharePoint environment for Reporting Services.
|  Note
|
| When the SQL Server installation is complete, follow the other sections of this topic to configure the SharePoint environment. This Includes installing the Reporting Services shared service and creating Reporting Services service applications. |
-
- Help Microsoft improve SQL Server features and services by clicking the check box to send error reports on the Error Reporting page.
Click Next.
- Review any warnings and then click Next on the Installation Configuration Rules page.
- On the Ready to Install page, review the installation summary and then click Next. The summary will include a Reporting Services SharePoint Mode child node that will show a value of SharePointFilesOnlyMode. Click Install.
- The installation will take several minutes. You will see the Complete page with the features listed and the status of each feature. You may see an information dialog indicating the computer needs to be restarted.
Make sure to do the above on all your Application and Web Front End servers
Step 2: Register and Start the Reporting Services SharePoint Service
| ![clip_image005[1]](//lh3.ggpht.com/--94SWzyZBbE/UiRlZTalRyI/AAAAAAAAL5k/PPZfwV1RMqk/clip_image005%25255B1%25255D_thumb.gif?imgmax=800 "clip_image005[1]") Note
|
| If you are installing into an existing SharePoint farm, you do not need to complete the steps in this section. The Reporting Services SharePoint service is installed and started when you ran the SQL Server installation wizard as part of the previous section of this document. |
| |
The following are the common reasons why you need to manually register the Reporting Services service.
· You installed Reporting Services SharePoint mode before SharePoint was installed.
· The account used to install Reporting Services SharePoint mode, was not a member of the SharePoint farm administrators group. For more information, see the section Setup Accounts.
The necessary files were installed as part of the SQL Server installation wizard, but the services need to be registered into the SharePoint farm. The SQL Server 2012 release introduces PowerShell support for Reporting Services in SharePoint mode.
The following steps guide you through opening the SharePoint Management Shell and running cmdlets:
1. Click the Start button
2. Click the Microsoft SharePoint 2013 Products group.
3. Right-click SharePoint 2013 Management Shell click Run as administrator. NOTE: the SharePoint commands are not recognized in the standard Windows PowerShell window. Use the SharePoint 2013 Management Shell.
4. Run the following PowerShell command to install the SharePoint service. A successful completion of the command displays a new line in the management shell. No message is returned to the management shell when the command completes successfully:
5. Install-SPRSService
6. Run the following PowerShell command to install the service proxy. A successful completion of the command displays a new line in the management shell. No message is returned to the management shell when the command completes successfully:
7. Install-SPRSServiceProxy
8. Run the following PowerShell command to start the service or see the following notes for instructions on how to start the service from SharePoint Central administration:
9. get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
![clip_image005[2]](//lh4.ggpht.com/-x-GbZ55RVy0/UiRlaxtItuI/AAAAAAAAL50/_J6YslPtrLo/clip_image005%25255B2%25255D_thumb.gif?imgmax=800 "clip_image005[2]") Important
|
If you see an error message similar to the following:
Install-SPRSService : The term 'Install-SPRSService' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. |
Either you are in the Windows Powershell instead of the SharePoint Management Shell or Reporting Services SharePoint mode is not installed. For more information on Reporting Services and PowerShell, see PowerShell cmdlets (Reporting Services SharePoint Mode)
.
You can also start the service from SharePoint central Administration rather than running the third PowerShell command. The following steps are also useful to verify that the service is running.
1. In SharePoint Central Administration, click Manage Services on Server in the System Settings group.
2. Find SQL Server Reporting Services Service and click Start in the Action column.
3. The status of the Reporting Services service will change from Stopped to Started. If the Reporting Services service is not in the list, use PowerShell to install the service.
![clip_image005[3]](//lh5.ggpht.com/-c5zOWkR-9Hw/UiRlcCNM1cI/AAAAAAAAL6E/EBAL6pxZkmc/clip_image005%25255B3%25255D_thumb.gif?imgmax=800 "clip_image005[3]") Note
|
If the Reporting Services service stays in the Starting status and does not change to Started, verify the ‘SharePoint 2013 Administration’ service is started in Windows Server Manager. |
Step 3: Create a Reporting Services Service Application
Before creating the service application, make sure you have created a Managed account which you can use for the new Application Pool you are going to use and make it a domain account!
This section provides the steps to create a service application and a description of the properties, if you are reviewing an existing service application.
1. In SharePoint Central Administration, in the Application Management group, click Manage Service Applications.
2. In the SharePoint ribbon, click the New button.
3. In the New menu, click SQL Server Reporting Services Service Application..
![clip_image005[4]](//lh3.ggpht.com/-9ExOAWnumms/UiRld7zX0DI/AAAAAAAAL6U/buHFn_yT98I/clip_image005%25255B4%25255D_thumb.gif?imgmax=800 "clip_image005[4]") Important
|
If the Reporting Services option does not appear in the list, it is an indication that the shared service is not installed. Review the previous section on how to use PowerShell cmdlts to install the Reporting Services service. |
4.
In the Create SQL Server Reporting Services Service Application page, enter a name for the application. If you are creating multiple Reporting Services service applications, a descriptive name or naming convention will help you organize your administration and management operations.
5. In Application Pool section, create a new application pool for the application (recommended). If you use the same name for both the application pool and the services application, it can make ongoing administration easier. This can also be affected by how many service applications you will create and if you need to use several in a single application pool. Consult the SharePoint Server documentation on recommendations and best practices for application pool management.
Select or create a security account for the application pool. Be sure to specify a domain user account. A domain user account enables the use of the SharePoint managed account feature, which lets you update passwords and account information in one place. Domain accounts are also required if you plan to scale out the deployment to include additional service instances that run under the same identity.
6. In the Database Server, you can use the current server or choose a different SQL Server.
7. In Database Name the default value is ReportingService_<guid>, which is a unique database name. If you type a new value, type a unique value. This is the new database to be created specifically for the services application.
8. In Database Authentication, the default is Windows Authentication. If you choose SQL Authentication, refer to the SharePoint administrator guide for best practices on how to use this authentication type in a SharePoint deployment.
9. In the Web Application Association section, select the Web Application to be provisioned for access by the current Reporting Services Service Application. You can associate one Reporting Services service application to one web application. If all of the current web applications are already associated with a Reporting Services service application, you see a warning message.
10. Click OK.
11. The process to create a service application could take several minutes to complete. When it is complete, you will see a confirmation message and a link to aProvision Subscriptions and Alerts page. Complete the provision step if you want to use the Reporting Services subscriptions feature or the data alerts feature. For more information, see Provision Subscriptions and Alerts for SSRS Service Applications.
Step 4: Activate the Power View Site Collection Feature.
Power View, a feature of SQL Server 2012 Reporting Services Add-in for Microsoft SharePoint Products, is a site collection feature. The feature is activated automatically for root site collections and site collections created after the Reporting Services add-in is installed. If you plan to use Power View, verify that the feature is activated.
If you install the Reporting Services add-in for SharePoint Products after the installation of the SharePoint Server, then the Report Server integration feature and the Power View integration feature will only be activated for root site collections. For other site collections, manually activate the features.
To Activate or Verify the Power View Site Collection Feature
1. The following steps assume your SharePoint site is configured for the 2013 experience version.
Open your browser to the desired SharePoint site.
2. Click Site Contents.
3. Click Settings.
4. In the Site Collection Administration group Click Site Collection Features.
5. Find Power View Integration Feature in the list.
6. Click Activate. The feature status will change to Active.
This procedure is completed per site collection. For more information, see Activate the Report Server and Power View Integration Features in SharePoint.
Additional Configuration
This section describes additional configuration steps that are important in most SharePoint deployments.
Configure Excel Services and PowerPivot
If you want to view Power View reports in an Excel 2013 workbook in SharePoint, an Excel Services Application on the farm needs to be configured to use a SQL Server Analysis Services Server in SharePoint mode. Also, the application pool security account used by the Reporting Services service application, must be an administrator on the Analysis Services Server. For more information, see the section “Configure Excel Services for Analysis Services integration” in Install Analysis Services Server in SharePoint Mode for SharePoint 2013 (SQL Server 2012 SP1).
Provision Subscriptions and Alerts
The Reporting Services subscription and data alert features may require the configuration of SQL Server Agent permissions. If you see an error message that indicates SQL Server Agent is required and you have verified SQL Server Agent is running, update the permissions. You can click the link Provision Subscriptions and Alerts on the create service application success page to go to another page for provisioning SQL Server Agent. The provision step is needed if your deployment crosses machine boundaries, for example when the SQL Server database instance is on a different machine. For more information, see Provision Subscriptions and Alerts for SSRS Service Applications
Configure E-mail for SSRS Service Applications
The Reporting Services data alerts feature sends alerts in e-mail messages. To send e-mail you may need to configure your Reporting Services service application and you may need to modify the e-mail delivery extension for the service application. If you plan to use the e-mail delivery extension for the Reporting Services subscription feature, the e-mail settings are required. For more information, see Configure E-mail for a Reporting Services Service Application
![clip_image005[5]](//lh3.ggpht.com/-diYbzlytYIU/UiRlfXnBhQI/AAAAAAAAL6k/vsWCGVBpHD0/clip_image005%25255B5%25255D_thumb.gif?imgmax=800 "clip_image005[5]")
Add Reporting Services Content Types to Content Libraries
Reporting Services provides predefined content types that are used to manage shared data source (.rsds) files, report models (.smdl), and Report Builder report definition (.rdl) files. Adding a Report Builder Report, Report Model, and Report Data Source content type to a library enables the New command so that you can create new documents of that type. For more information, see Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode).
Reporting Services provides predefined content types that are used to manage shared data source (.rsds) files, report models (.smdl), and Report Builder report definition (.rdl) files. Adding a Report Builder Report, Report Model, and Report Data Source content type to a library enables the New command so that you can create new documents of that type.
To add content types to a library, you must be a site administrator or have Full Control level of permission.
The Reporting Services content types and content type management will automatically be enabled in all document libraries for existing site collections created from the following site template types:
- Business Intelligence Center
Sites created after the Reporting Services integration will not have the Reporting Services content types enabled.
![clip_image005[6]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvJOPBcxhA4TqECMY46G0FARvZlAw46H-tS-LhdnMyVVIU57FqsDIB7e45ejXrc_ZZZsR0yqC_zonhJf5o9hyphenhyphen0MNtWn5vbiyldNEk2O07aHac4o8-DPZc1otyhJCs9uxqzrhKOPAIJ6yY/?imgmax=800 "clip_image005[6]") Tip
|
If you have not previously configured content types for a library, first enable management of content types, then enable the Reporting Services content types. See the procedures on enabling content type management in a single document library. |
Enable Content Types in all document libraries in an Existing Business Intelligence Center
1. To enable the content types and content management in all document libraries in an existing Business Intelligence Center site, you can toggle the Reporting Services integration feature.
2. Go to Site settings.
o In SharePoint 2013, click the Settings icon. 
o In SharePoint 2010, click Site Actions, then click Site Settings.
3. Click Site collection features.
4. Find the Report Server Integration Feature and click Deactivate.
5. Refresh the browser then click Activate for the Report Server Integration Feature.
To enable content type management for a document library (SharePoint 2013)
1. Open the library for which you want to enable multiple content types.
2. Click Library in the ribbon.
3. On the Library ribbon, click Library Settings. If you do not see Library Settings or the button is disabled, you do not have permission to configure library settings, including content types.
4. In the General Settings section, click Advanced settings.
5. In the Content Types section, select Yes to allow management of content types.
6. Click OK.
To Add Reporting Services content types (SharePoint 2013)
1. Open the library for which you want to add Reporting Services content types.
2. On the ribbon, click Library.
3. Click Library Settings.
4. Under Content Types, click Add from existing site content types.
5. In Select site content types from, select SQL Server Reporting Services Content Types.
6. In the Available Site Content Types list, click Report Builder, and then click Add to move the selected content type to the Content types to add list.
7. To add Report Model and Report Data Source content types, repeat the previous step.
8. When you finish adding content types, click OK.
9. Note, if the content type group SQL Server Reporting Services Content Types is not visible on the Add Content Types page, one of the following conditions is true:
o The Reporting Services add-in for SharePoint products has not been installed. For more information, see Install or Uninstall the Reporting Services Add-in for SharePoint.
o All of the Reporting Services content types have already been added to the library. If all the content types are part of a library, then the group is removed from the Add Content Types page. If you delete one or more of the Reporting Services content types, then the group SQL Server Reporting Services Content Typeswill be visible on the Add Content Types page.
Activate the Report Server File sync Feature
If users will frequently upload published report items directly to SharePoint document libraries, the Report Server File Sync site level feature will be beneficial. The file sync feature will synchronize the report server catalog with items in document libraries on a more frequent basis. For more information, see Activate the Report Server File Sync Feature in SharePoint Central Administration.
![clip_image003[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgoPHFodyestds4YucP9BoyuFGd3Nm_dCUlWTIFyuTPmsUVrn5EeetEtHbhgKxTD2TxJoXxZAdA1qYdsbk3b-NGhX_svc9I3MU8zXqHr6PSvfv4IaTWtUKyTGzMZ3lKYsLeJZdHdvP8OX0/s1600-h/clip_image003%25255B1%25255D%25255B2%25255D.gif "clip_image003[1]"){kind=small}
![clip_image002[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEijYgC2CWv2rfaOZ4CIx94lRIqrs12ySfxUX1KRjyjTaw7cvz4UmASt0ZveTO6YjTXi4dSLqJP0PmWk9yaIVvfRkWi3bhP7L_Q2bq4nBeRBcCgDSdiMa_IozlktW81KoDisMsTqqr2_qhI/s1600-h/clip_image002%25255B1%25255D%25255B2%25255D.gif "clip_image002[1]"){kind=small}
![clip_image005[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhaqGTCP6MxGIZWafeYYfjFU5U2v7LGGMs3YmV5nSaxC9Iu32LYz7vQbO0GsdpmQUqGBb4H2tRP6BltsVVP2Jjov9yFSU21u7Ik83vB_p4ztIFhFy2-46OLMd7v2JBQUzJTDubo7e9hBXI/s1600-h/clip_image005%25255B1%25255D%25255B2%25255D.gif "clip_image005[1]"){kind=small}
![clip_image005[2]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCGQPHndE_MSd9LmeByUwyUe5pC3YurCUjCvOI5eiOElUxt7VqrVy9-rYQYqH4cqD-cz58Pq9qzpVnh0Br0jRnprIam593AyG-RfsLiJcRjDPPL0p3q7eSyvepRNFVwbEGXVBoRZU-tgQ/s1600-h/clip_image005%25255B2%25255D%25255B2%25255D.gif "clip_image005[2]"){kind=small}
![clip_image005[3]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPHW6cbg97ICXYu5gACcseTqjEZ3B8fAwEjFZX8AvfJGzryLgf11YX3P49ppYa-pWWnbQWG-o0nQeJz4aZ-hRHK5KOo9PzZyps0pQyYDWau7xZ4hc6W6uHjB1yr_vbSar8LHjoMoPS9UE/s1600-h/clip_image005%25255B3%25255D%25255B2%25255D.gif "clip_image005[3]"){kind=small}
![clip_image005[4]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhN-bDUl3tw357WyuKA_8NyT9chrkxNx7V0MgM8m4QhIHOiURzO49h7oyenJluFsvvTT1sOeuvHQpw5YskOv-Hybkvx2nErX5_6Z97-zOREGh7WlgYLE1jj4fl9Eh0nMuCATrbss2FCgiQ/s1600-h/clip_image005%25255B4%25255D%25255B2%25255D.gif "clip_image005[4]"){kind=small}
![clip_image005[5]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgbO4JUMUPhuV-1PNYPxAikOGDvoILd_w93qL7zqdlfvZhKGm5fkCM8ePXe6vl0XF1RHIoInx0vsQN6lAUQIDaiAHSmu_Rb_7gnPDctL7klOqAf5TPyaI0S7TXvNd7vCn5tmcMT0XlMvec/s1600-h/clip_image005%25255B5%25255D%25255B2%25255D.gif "clip_image005[5]"){kind=small}
![clip_image005[6]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgKQWq4iaZsRYUz1TnwbNHIcP34hbgUJMKZ75Rgl-ad2T5xmPDStuiEH4CfTrd5oLn4hJke9iB0JQKbV16jqoPy55S2_fisN9GmsPuz7uN9Po1CrwFgYCtUcrm2IOkJ6C0sHZUuG7pcHzU/s1600-h/clip_image005%25255B6%25255D%25255B2%25255D.gif "clip_image005[6]"){kind=small}
![clip_image005[7]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfxri5cmXZMFrxcE0aHmpxpjIwR2_uXufk9kZb4Ss2lUdqoSkw8Ge5O4gipj1lgbNEOO5tlOf6n5BM35ZINFSG6cIuBQQ-nJMubR0AWCTNEE0uqNb0jJdV_RkWRJS1YZ7vHUDEdx4Xf50/s1600-h/clip_image005%25255B7%25255D%25255B2%25255D.gif "clip_image005[7]"){kind=small}
