Microsoft distributes Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release.
Symptoms
Consider the following scenario:
-
You install Microsoft SQL Server 2008 R2 Reporting Services (SSRS) on a computer.
-
You install Microsoft SharePoint Server 2010 and then configure Reporting Services in SharePoint Integrated mode by using the Trusted Account mode.
-
You deploy two reports to the SharePoint Document Library. In report A, you add a drillthrough report link to report B.
-
You add a Report Viewer web part to a webpage on the SharePoint site. You configure the Asynchronous Rendering property of the Web part to False. Then, you point the web part to report A.
In this scenario, report A is displayed successfully in the web part. However, when you click the hyperlink to the drillthrough report, the hyperlink fails, and you receive the following error message:
The report execution Session_ID has expired or cannot be found. (rsExecutionNotFound)
Cause
This problem occurs because of a bug in the Report Viewer web part control. The trusted account header value is not set in the drillthrough report when a drillthrough action is performed in the Report Viewer web part control. Therefore, the session data does not belong to the correct session owner of the drillthrough report.
Resolution
Cumulative update information
The fix for this issue was first released in Cumulative Update package 6 for SQL Server 2008 R2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489376 Cumulative Update package 6 for SQL Server 2008 R2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Workaround
To work around this issue, use one of the following methods:
-
Configure the SSRS SharePoint Integrated mode by using the Windows Authentication mode.
-
Configure the Asynchronous Rendering property of the Report Viewer web part to True. By default, this property is set to True. You can leave the integration setting in Trusted Account mode.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about how to configure a report server to run in a deployment of a SharePoint product, visit the following Microsoft Developer Network (MSDN) website:
How to: Configure Report Server Integration in SharePoint Central AdministrationFor more information about how a report can contain links to other reports, visit the following MSDN website:
How to: Add a Drillthrough Action on a Report (Reporting Services)For more information about how to configure the ReportViewer web server control for asynchronous rendering, visit the following MSDN website:
Configuring ReportViewer for Asynchronous RenderingFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
