Skip to main content

Integrating Sharepoint 2010 and SQL Reporting Services 2008


There are only 6 main steps to achieve this task assuming you already have an instance of SQL Server Reporting Services and Sharepoint 2010.
I had created this starting from a clean installation of SQL Reporting Services so this guide will discuss the steps on configuring your SQL Reporting Services 2008 for integration with Sharepoint 2010.
Step 1 : Configuring SQL Reporting Services – Web Service URL.
Simply go to Reporting Services Configuration Manager and choose Web Service URL and populate the following needed information. The fields are named properly so I guess theres no need for further explanation.  What this does is that it configures the IIS for you depending on what Virtual Directory names you had declared
Step 2 : Configuring SQL Reporting Services – Create a Report Database
Same here fields need no further explanation except for one which is Native Mode and Sharepoint Integrated mode which I will explain below.
Choose create a database or if you already have one choose an exisiting, for this example we will create a new one
Connect to the database where you want your Report Data to be stored
Give it a Name and a Report Server Mode.
With Sharepoint Integrated Mode the report rdl’s are stored on SharePoint and not in the Report Database.  For this instance we will use the Sharepoint Integrated Mode
Specify the credentials that the report server will use to connect to the database.
Review your configuration.
Then wait while its configured.
Step 3 : Configuring SQL Reporting Services – Create a Report Manager URL
What this does is that it configures the IIS for you depending on what Virtual Directory names you had declared.
That’s it at this point your report server is configured for Sharepoint Integration 2010
Step 4 : Sharepoint Integration Configuration – Reporting Services Integration.
Simply go to SharePoint 2010 Central Administration then General Application Settings then choose Reporting Services Integration.
Now populate the fields using the Web Service URL you had configured a while ago on Step 2 of this guide.
Once done you will see the Activation State message.
Step 5 : Sharepoint Integration Configuration – Add a Report Server to the Integration
Now add the report server by putting the Server Name and the Server instance.
At this point its all done, all you have to do now is try it out
Step 6 : Verify by checking the server and uploading a report
To verify if its now integrated, go to Site Settings on your Sharepoint Site then Site Collection Features.
Check if the Report Server Integration Feature is Active if not just click activate
Now try to use the SQL Server Reporting Services Webpart
Or you can also upload a report from a library.

Popular posts from this blog

Cascading drop down column in a SharePoint List

This article will show how to use codeplex project to achieve Cascading drop down columns in SharePoint list. This article will show how to achieve parent child relationship in column of SharePoint list.   Objective This article will show how to use codeplex project to achieve Cascading drop down columns in SharePoint list. This article will show how to achieve parent child relationship in column of SharePoint list. Step 1 Download the project from codeplex . Choose WSP file to download. To download the project Click here Step 2 After downloading the WSP add the solution using STSADM command. Navigate to BIN folder and add the solution. Command C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN> stsa dm -o addsolution -filename c:\Stoneshare.CascadingDropDown.WithFilter.wsp Step 3 Open Central ADMIN and deploy solution. Navigate to Operation -> Global Configuration -> Solution Management. Select the Global Deployment option. St...

How to deal with SharePoint 2010 exception "An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error"

Scenario: You receive the below exception when you try to logon to a site that has been configured to use Claims Based Authentication with a custom membership provider using FBA credentials: Event ID from Event Log  - 8306 An exception occurred when trying to issue security token: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. Explanation: This error started to appear in our QA environment which does not have Visual Studio installed. I have tried starting the service "Claims to Windows Token Service" but that did not help either. I have made sure that all config...

Create Rating Visual Web Part Using Visual Studio 2010,

Create Rating Visual Web Part Using Visual Studio 2010,  also Apply Rating Settings using c#   Back End Design  Register Assembly    <%@ Register Tagprefix="SharePointPortalControls" Namespace="Microsoft.SharePoint.Portal.WebControls" Assembly="Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> Add Control. <div>    Average Ratting :    <SharePointPortalControls:AverageRatingFieldControl ID="PageRatingControl" runat="server"/> </div>