Rendering Local Mode Reports in the Report Viewer (Reporting Services in SharePoint Integrated Mode)
In previous versions of Reporting Services, the SharePoint farm was required to be connected to a Reporting Services report server configured in SharePoint integrated mode so the Report Viewer control could render reports. This approach is called remote mode or connected mode.
Starting with the SQL Server 2008 R2 release, you can render reports without integrating your SharePoint farm with a Reporting Services report server. Instead, you can use the Report Viewer to directly render reports from SharePoint when the data extension supports local mode reporting. This approach is called local mode. The following is a list of the data processing extensions that support local mode reporting:
Microsoft Access 2010 reporting extension. For more information on Access Services, see Using Access Services with SQL Reporting Services: Installing SQL Server 2008 R2 Reporting Services Add-In (SharePoint Server 2010).
The Reporting Services SharePoint list data extension. For more information on the SharePoint List Data Extension, see Data Sources Supported by Reporting Services (SSRS)
Custom data processing extensions can also be developed to support local mode. For more information, see Implementing a Data Processing Extension.
Local mode supports rendering reports that have an embedded data source or a shared data source from an .rsds file. However, you cannot manage the report or its associated data source. If you try to do this, you will receive an error that this is not supported in local mode. Managing data sources in the SharePoint site is supported in only connected mode.
As with previous versions, you cannot embed user names and passwords in the .rsds file.
Configuring Local Mode Reporting
Local mode requires ASP.NET session state. The installation of Access services will enable ASP.Net sessions state. You can also enable using PowerShell.
Open the SharePoint 2010 Management Shell.
Type the following command:
When prompted, type the name of your database.
Perform an IIS reset.