How to configure Reporting functionality to SharePoint 2013 if RS is already installed as Native mode
-
Wednesday, January 23, 2013 8:49 AM
Is it possible to publish reports to SharePoint if SQL Server 2012 reporting service is on native mode?
How to do it?
I have SharePoint 2013 and SQL Server 2012. I have created cube and reports with its data tools. This is single server environment.
This is what I have done:
A) I can successfully see from SQL Server installation tool that "Reporting Service-SharePoint" and "Reporting Services Add-in for SharePoint Products" are checked.
B) I don't see Reporting Services under the Manage Service Application of the SharePoint Central Admin.
c) When I choose report from reporting service project and I click deploy, it asks Reporting Services Login, but it does not accept admin logins. Server path should be valid.
I got idea from following instruction that I should register and start the Reporting Services SharePoint service
http://msdn.microsoft.com/en-us/library/jj219068.aspx
C) I tried to run command Install-SPRSService, but it was not recognized cmdlet command.D) I see from Reporting Service Configuration Manager that Reporting Server Mode is Native. Report Service Status is Started.
Kenny_I
All Replies
-
Friday, January 25, 2013 3:17 AMModerator
Hi Kenny_I,
Since the release of SQL Server 2012, Reporting Services SharePoint Integrated mode has been changed from a Windows Service to be a SharePoint Shared Service. In this way, Reporting Services Configuration Manager no longer supports Reporting Services SharePoint mode, and all the configurations of SharePoint mode is completed using SharePoint Central Administration.
In SSRS 2008 R2 or lower version, only one report server (either native mode or SharePoint integrated mode) can be active at one time in one SSRS instance. In SSRS 2012, the report server that runs in SharePoint integrated mode and the report server that runs in Native mode work separately at the same time in one SSRS 2012 instance. So, in this issue, you don’t need to care about the report server that runs in native mode when you work with the report server that runs in SharePoint mode.
First, please install SQL Server 2012 SP1 which introduces more BI features.
For the issue you encounter when running the commands to register the Reporting Services SharePoint Service, it may occur if you run the commands in the Windows Powershell instead of the SharePoint Management Shell. Please launch the SharePoint Management Shell by clicking Start-> All Promgrams -> Microsoft SharePoint 2013 Products -> SharePoint 2013 Management Shell. Then, please continue the steps in the following document or blog to create a Reporting Services Service Application:
- Install Reporting Services SharePoint Mode for SharePoint 2013
- Installing and configuring SQL Reporting services on SharePoint 2013
After a SSRS Service Application is created properly, to deploy the project to the SharePoint integrated mode report server, please see the project property settings in the following document:
Project Property Pages Dialog BoxRegards,
Mike YinIf you have any feedback on our support, please click here
Mike Yin
TechNet Community Support- Edited by Mike YinMicrosoft Contingent Staff, Moderator Friday, January 25, 2013 3:21 AM
-
Monday, January 28, 2013 11:15 AM
I install SQL Server 2012 SP1 and I got now Reporting Service Application. Thanks for Tip!
I can now deploy reports from data tools and see then in the http://server/ReportServer.
Now how can see them in the document/report library and see reports integrated to the Sharepoint 2013?
I don't see any report library app to be added in the sharepoint site.
I configured Reporting Services Integration. I got error "Report Server WMI Provider error: Invalid namespace". URL and user should be ok. Why this occur?
Kenny_I
-
Tuesday, January 29, 2013 1:41 AMModerator
Hi Kenny_I,
Thank for your posting.
The “Reporting Services Integration” options in SharePoint Central Administration only apply to SSRS 2008 and SSRS 2008 R2. In SSRS 2012, we only need create a Reporting Services Service Application and create a site collection for the Web Application that the SSRS Service Application is associated to. For the detailed steps about how to create a site collection, please see:
Create a site collection (SharePoint Server 2010)After we create a site collection for the target Web Application, we can go to the site, and create a Document Library. Then, follow the Step 17- Step 19 in the following blog to add SSRS content types for the document library:
Installing and configuring SQL Reporting services on SharePoint 2013For example, the site collection is http://<Server Name>/sites/ssrs. Then, we need to specify http://<Server Name>/sites/ssrs or http://<Server Name/ as the TargetServerURL when deploying the reports. Besides, we need to specify full path of the target folders for reports and shared data sources. For example, specify http://<Server Name>/sites/ssrs/Data Sources for the shared data sources in the project (need to create the “Data Sources” document library first), and specify http://<Server Name>/sites/ssrs/Reports for the TargetReportFolder.
Regards,
Mike Yin
TechNet Community Support- Marked As Answer by Mike YinMicrosoft Contingent Staff, Moderator Sunday, February 03, 2013 4:42 PM
-
Tuesday, January 29, 2013 7:10 AMThanks for your help!
In SharePoint site, I have create document library and added content type Reports. Url is http://server/Documents/Forms/AllItems.aspx
In Data Tool, I have opened project Properties. Deploying with TargetServerURL http://server/ReportServer is working, but not working with http://server or http://server/Documents.
I got path error when set TargetReportFolder value as http://server/Documents and deployed it.
Where I should define the exact folder of report library?Kenny_I
-
Tuesday, January 29, 2013 7:31 AMModerator
Hi Kenny_I,
When you specify http://<Server Name>/reportserver as the TargetServerURL, it actually deploys the report to the report server that runs in native mode rather than the report server that runs in SharePoint integrated mode.
From your description, the site collection you created is http://<Server Name>, and the document library name is “Documents”. The issue may occur if you are not specifying a proper URL for the TargetDataSourceFolder property.
Here, you can create another document library to store the shared data sources, let’s name it to “Data Sources”. Then, you can set the properties of the project as follows in the SSDT:
TargetDataSourceFolder: http://<Server Name>/Data Sources
TargetReportFolder: http://<Server Name>/Documents
TargetServerURL: http://<Server Name>Besides, clear the textbox for the TargetReportPartFolder item.
If the issue persists, please post the error message for further analysis. If possible, please post screenshots to show us the issue.
Regards,
Mike Yin
TechNet Community Support -
Tuesday, January 29, 2013 8:17 AM
Thanks. I'm now close. I followed your instructions with project properties and file is now deployed to the document library.
However I get error when opening the file at SharePoint library.
-
An error has occurred during report processing. (rsProcessingAborted)
-
Cannot impersonate user for data source 'ABC_DataSource1'. (rsErrorImpersonatingUser)
- Can not convert claims identity to windows token. This may be due to user not logging in using windows credentials. (rsClaimsToWindowsTokenLoginTypeError)
-
Cannot impersonate user for data source 'ABC_DataSource1'. (rsErrorImpersonatingUser)
Kenny_I
-
An error has occurred during report processing. (rsProcessingAborted)
-
Tuesday, January 29, 2013 8:57 AMModerator
Hi Kenny_I,
Based on the error message, the issue may occur if the Claims to Windows Token Service (C2WTS).
The SharePoint Claims to Windows Token Service (C2WTS) will be required if you want to use windows authentication for Data Sources that are outside the SharePoint farm. This is true even if the user accesses the data sources with Windows Authentication because the communication between the web front-end (WFE) and the Reporting Services shared service will always be Claims authentication.
To configure the C2WTS, please see:
http://msdn.microsoft.com/en-us/library/hh231678.aspxIf the issue persists, create another web application and set it to use Classic mode authentication rather than Claims mode authentication. Then, configure the Service Application to associate with the new Web Application and check the issue again.
Hope this helps.
Regards,
Mike Yin
TechNet Community Support -
Tuesday, January 29, 2013 10:43 AM
I looked article on http://msdn.microsoft.com/en-us/library/hh231678.aspx
I says about Claims to Windows Token Service followings. Does it mean that no way I can deploy reports if I have single server farm? I have currently single server environment.
Note: Some of the configuration steps may change, or may not work in certain farm topologies. For instance, a single server install does not support the Windows Identity Foundation C2WTS services so claims to windows token delegation scenarios are not possible with this farm configuration
Kenny_I
-
Tuesday, January 29, 2013 12:16 PMModerator
Hi Kenny_I,
Thanks for your posting.
From the MSDN document, we can read that the Windows Identity C2WTS services are not supported by the SharePoint single server farm topology. Here, I suggest that you configure the data source to use stored credentials instead. If it doesn't work, please create a new Web Application that uses Classic authentication and check the issue again.
Reference:
Update Credentials in Report Data Sources from a SharePoint SiteRegards,
Mike YinIf you have any feedback on our support, please click here
Mike Yin
TechNet Community Support- Marked As Answer by Mike YinMicrosoft Contingent Staff, Moderator Sunday, February 03, 2013 4:43 PM


