Skip to main content

SharePoint 2010 Reporting Services with SQL Server 2008 R2

Setting up Reporting Services for a SharePoint 2010 in integrated mode can be done in less than 30 minutes if you have the infrastructure ready. However there are a few things to take care of if we are in a SharePoint farm environment with different servers handling different roles.

To get Reporting Services to work in SharePoint Integrated mode requires SharePoint object model. Either we install SharePoint object model on our database server running Reporting Service or install SQL Server Reporting Service on a SharePoint application server.

Here are a few things to take care of:

1. Use a domain account in the Reporting Services Configuration Manager

2. In the Reporting Services Configuration Manager wizard, click on Apply in different screens before navigating away.

3. Reporting Services Add-in is required on SharePoint Servers; it is part of the SharePoint 2010 pre-requisite installer. It can also be downloaded and installed separately on SharePoint Servers.

To get this working we have configuration to do in the SharePoint Central Administration website and on the Reporting Services Configuration Manager. 

Here are the steps:

1. Install Reporting Service on a SharePoint application server or install SharePoint web role on the SQL Server with Reporting Service enabled.

2. Open Reporting Services Configuration Manager – Service Account – provide a domain account to run Report Server Service. Click Apply.

3. In the section Web Service URL, provide a name for virtual directory in IIS for Report Server web service. Other settings in this page can be left alone unless you need the website to use SSL. Click Apply and if you see an hyperlink under the heading Report Server Web Service URLs, the configuration is proper.

4. In the next screen named Database, create a new Report Server database and make sure to select SharePoint Integrated Mode. Once required information is entered and connection is tested, click Apply.

5. Report Manager URL is not relevant for an SharePoint integrated environment, click Apply and navigate to next screen.

If we click on the report manager URL we would receive an error at this point because we don't access reports through report manager in SharePoint integrated mode, we access through SharePoint.

We are almost done with the configuration here; make sure you backup encryption keys before closing the configuration manager.

6. Open Internet Explorer as administrator and navigate to Central Administration – General Application Settings – Reporting Services and provide the web service url we found in the web service url screen in Reporting Services Configuration Manager.

7. Under Authentication Mode, select Windows Authentication if the web application to host reports is using classic authentication, if its using claims then select Trusted Account.

If the web application is using claims authentication it would be using Trusted Authentication irrespective of what we select here.

8. Provide credentials of a user who has administrative privilege on the server hosting Report Server. Also we have an option to activate the Reporting Service feature on all existing site collections or on specific ones. Click Ok.

9. To test the configuration navigate to Report Server url.

That concludes the configuration and now we can start deploying reports using tools like Microsoft Business Intelligence Development Studio (BIDS) or directly using Report Builder. 

Happy reporting!



Labels:

Comments

Post a Comment

Popular posts from this blog

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...
Post a Comment
Read more

Page layout HTML changes not reflected in associated aspx

I had this issue for quite sometime with a SharePoint Online project I was working on. I use Design Manager to create a new layout page and add snippets to the html layout. I would create webpart zones, add my webpart snippets on to the html, save and publish but the resulting aspx page wouldn't have any of my webparts in it. I checked it from SPD 2013 and everything looks perfect, I can see all the code snippets in there. It was really strange and I had no clues. I had some content search webparts in the layout and one content editor webpart with a link to a text file with some css in it. After countless hours on the internet I read about few other people having similar issues when they had custom css on the layout pages to hide quick launch. I tried removing my content editor webpart and everything seems to be normal. A new page created using the layout had all the webparts in it and even the layout preview was displaying fine. I needed this css somewhere on the page and ...
Post a Comment
Read more

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more