SQL Server 2012 (“Denali”): Reporting Services in SharePoint integrated mode
In SQL Server 2008, if you wanted to run Reporting Services in SharePoint integrated mode, these where the steps you took (see How to: Install and Configure SharePoint Integration on a Stand-alone Server):
- Install SQL Server 2008 and on the on the Feature Selection page select the Database Engine Services as well as Reporting Services
- During the install, when you get to the on the Reporting Services Configuration page, choose “Install the SharePoint integrated mode default configuration”
- When the SQL Server 2008 installation is finished, run the SharePoint 2010 Products Preparation tool to install the Microsoft SQL Server 2008 R2 Reporting Services Add-in for Microsoft SharePoint Technologies 2010, or you could instead install it separately via this download
- Install SharePoint 2010
- Run the SharePoint Products Configuration Wizard, choosing the database engine you installed in step #1
- Configure the report server integration features via the SharePoint Central Administration. Do this by going to the Manage Service Applications screen, click New, and choose “SQL Server Reporting Services Service Application”
In SQL Server 2012, this has been changed. When installing SQL Server 2012, on the Feature Selection page, as before you choose Database Engine Services, but now on this page is the option to choose “Reporting Services – SharePoint”, so step #2 above it not needed (this is also an option to choose “Reporting Services – Native”). This is also an option called “Reporting Services Add-in for SharePoint Products”, so step #3 above is not needed either. Note that the “Reporting Services Add-in for SharePoint Products” is a newer version than what is installed with the SharePoint 2010 Products Preparation tool, with one of the new features it installs being Power View. Steps #4-6 are the same.
Great article, accurate information indeed!
The changes in SSRS 2012 are significant, being an architecture change from SSRS 2008 R2. I could find that the differences, regarding sharepoint integration, were:
In SSRS 2012 integrated with sharepoint:
1) No SSRS SQL Server instance of type sharepoint integrated is used anymore.
2) No SSRS configuration manager is used anymore.
3) No Reporting Services Integration option used anymore, under Sharepoint Admin Site.
In SSRS 2012, sharepoint takes care of all SSRS web service behavior. Reporting Services is now a service application after you install 2 options from sql server 2012 install media: Reporting Services – SharePoint and Reporting Services add-in for SharePoint 2010 Products. Both are under SHARED COMPONENTS (no new database instance as it was in SSRS 2008 R2).
There is a caveat I’m still to get solved: Report deployment to a sharepoint library does not work anymore, from a report server project in Visual Studio 2010 Shell (now named SQL Server Data Tools, formerly BIDS), because of the deploy properties TargetServerURL, TargetReportFolder, etc). There is a vast amount of information on msdn and on independent blogs on how to fill these properties correctly, but all for 2008 R2 version only. What about now, for SSRS 2012, with the new architecture?
I tried using different TargetServerURL project properties, and could come up with some conclusions: Sharepoint integrating with SSRS 2012 does not “expose” a /ReportServer URL anymore, as it was before. In a SSRS 2008 R2 integrated mode configuration, the url http://servername/ReportServer responded with the root directory for folder listings, indicating reportserver was listening… Now in SSRS 2012 I can only get a 404 not found page when trying to use http://servername/ReportServer.
The only way to get SSRS 2012 to respond was to use the following syntax: http:///_vti_bin/reportserver. The behavior of this reponse is the same as it was in 2008 R2. I figured that out from this post: http://www.duncansutcliffe.com/?p=22. Let me quote what Duncan Sutcliffe says: “There’s a problem with SQL Server 2012 SSRS running in integrated mode, though. It runs as a SharePoint managed service so it doesn’t have its own web service URL any more.”
Okay, then I tried setting TargetServerURL to “http:///_vti_bin/reportserver”, apparently it got reporting services to answer, but the another error came up: The path of the item ‘/http://ServerName/site/reportlibrary’ is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. —> System.UriFormatException: Invalid URI: The format of the URI could not be determined.
I’m stuck at this point, still need advice from Microsoft specialists. By the way, it intrigues me as no one came up with such an issue like this one yet, after doing a lot of research throughtout blogs, forums and msdn. Glad if anyone could help.
Was this resolved by you or any others? is there anything further to add?
Hi James,
Quick Question: I no longer have the setup files for SQL server 2012 and I would like to change the mode for my reporting services from Native to Sharepoint Integrated mode. Is there any other manner in which I could make this change?
Yes, this link explains how: http://blogs.msdn.com/b/dynamicsgp/archive/2012/03/01/moving-sql-server-reporting-services-from-native-mode-to-sharepoint-integrated-mode.aspx