Article ID: 2407088 - Last Review: October 18, 2010 - Revision: 1.0 FIX: "Sys.ArgumentNullException" error occurs when you open a drillthrough report in a Report Viewer Web part if you use the SharePoint Integrated mode in SQL Server 2008 R2 Reporting Services
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. On This PageSYMPTOMSConsider the following scenario:
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:
CAUSEThis issue occurs because the ReportViewer control does not generate the report correctly. RESOLUTIONCumulative update informationSQL Server 2008 R2The 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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. WORKAROUNDTo 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: REFERENCESFor 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
(http://support.microsoft.com/kb/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:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates | Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
