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 run Microsoft SQL Server 2008 R2 Reporting Services (SSRS) in the SharePoint Integrated mode.
-
You integrate a Microsoft SharePoint 2010 site with SSRS 2008 R2.
-
You run the SharePoint site in debug mode.
-
You deploy a report to a document library on the SharePoint site. The report contains a drillthough report.
-
You add a Report Viewer Web part to a SharePoint page to display the report.
-
You click the drillthrough link to open the drillthrough report in the SharePoint page.
In this scenario, you receive an error message that resembles the following:
Message: Sys.ArgumentNullException: Value cannot be null.
Parameter name: panelsCreated[6]
Line: 129
Char: 12
Code: 0
URI: http://ServerName/ScriptResource.axd?d=eIta46jBcyLp_5IiiP-xPYuM8iTgFWIJYJ1hdQQhytwzGZrxHUy3xfhvGgvjnG17BofUwEtaQ7Yik54n3MpmW77MX1gjt2yj-Zgalo8nheYxZrca6zgrx0VoNFUyBrAw0&t=ffffffffec2d9970
Note This issue usually occurs when you use the SharePoint Integrated mode. Additionally, this issue may also occur when you use the Native mode if the following conditions are true:
-
You use the WebForms ReportViewer control that was released together with Visual Studio 2010 in a webpage.
-
You set the ShowToolbar property of the control to False.
-
You run the website in debug mode.
-
You configure some elements of the page to listen to the PageRequestManager.pageLoaded event.
Cause
This issue occurs because the ReportViewer control does not generate the report correctly.
Resolution
Cumulative update information
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2345451 Cumulative Update package 4 for SQL Server 2008 R2 Note 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
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around this issue, turn off the debug mode in the Web.config file of the SharePoint site. To do this, set the debug property of the compilation tag to false in the Web.config file.
The following is a sample of text that demonstrates the debug property of the compilation tag set to false:
<?xml version="1.0" encoding="utf-8"?>
<<configuration>
...
<system.web>
...
<compilation defaultLanguage="c#" debug="false" ... />
References
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor 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
