Today I want to highlight the following subject: “SQL Server Reporting Services”. The procedures in this topic guide you through a single server installation of a Reporting Services report server in SharePoint mode. The steps include running the SQL Server installation wizard as well as additional configuration tasks that use SharePoint 2013 central administration. The topic can also be used for individual procedures for updating an existing installation, for example to create a Reporting Services service application.
First, Install the Service The first thing you need to make sure you do is install the service on SharePoint. Run the following PowerShell commands in SharePoint 2013 Management Shell as an administrator.
Second, Create the Service Application After you install the service in Central Administration you will now have the option to create a new SQL Server Reporting Services Service Application. Go to Application Management group, click Manage Service Applications and create a new service application. If you don’t see this option that means the above steps weren’t successful in creating the service. So make sure you have that completed before you try to create a new service application.
Third, Activate the Powerview Feature To activate the feature, go to the site collection features and find the feature Power View Integration Feature in the list and click Activate.
If you want to know how to configure it on SharePoint 2010; please refer to http://www.gknzcfc.net/subsite/how-to-configure-reporing-services-in-sharepoint2010.html
1. The first step you should do is connecting to the SQL server and open “Reporting Services Configuration Manager”
2. Secondly specify a Managed User and click on apply.
3. When Reporting Services Configuration Manager accepts the User that you provided please go to the following page “Web Service Url” and provide the following
4. After providing all the information that Reporting Services needs you can click on apply and you should see appear “creating virtual directory” and “url was successfully reserved”
5. Now, on the next tab please click “Database”. Actually you should see that any of the following has been filled. If this is the case do not worry J
6. Click on “Change Database”
7. There should be a new wizard on the screen asking you a few questions. On the first question please select “Create a new report server database”
8. Click Next
11. Click Next
12. Provide now a Service Credential to run you’re Reporting Services. Please do not like me, and don’t be lazy and create a realManaged Account =^)
13. Click Next
14. Finally, this was the last step and now you can install your Report Server.
15. After a while, you should see on each value a “success”
16. If this is the case you can click finish and close the wizard
18. This is the last screen of configuration on Reporting Services Configuration Manager. Provide a Virtual Directory and click on Apply.
19. Again you should see “Creating Virtual Directory” and “The URL was successfully reserved”
22. We have to configure Reporting Service now on our SharePoint Server but there is a little problem. We configured our SSRS after configuring SharePoint and SharePoint Server has any idea about what SSRS is.
23.So Microsoft tells us to execute the following PowerShell scripts to create our Service Application.
24. Connect to your Central Administration
25. Go to Manage Service Application
26. And create the new service “SQL Server Reporting Services Service Application”
Ed Price - MSFT edited Revision 1. Comment: Title, tags
Ed Price - MSFT edited Original. Comment: Technical voice, title, tags
You need to clarify this article. According to TechNet (msdn.microsoft.com/.../gg492276.aspx):
"The Reporting Services Configuration Manager is no longer required or supported to configure and administer Reporting Services SharePoint mode. Use SharePoint Central Administration to configure a report server in SharePoint mode."
Your article incorrectly directs users to configure SSRS 2012 using the Reporting Services Configuration Manager. This is no longer the case in SQL 2012/SP 2013. The wizard actually fails with an error.
This article would be appropriate if the SQL Reporting instance was SQL 2008 R2. Then you would need to uses the Reporting Services Configuration Manager.