FIX: rsInternalError error when you export a report that contains a Tablix control in SSRS 2008 R2 or in SSRS 2012

Article translations Article translations
Article ID: 2707015 - View products that this article applies to.
Expand all | Collapse all

On This Page

Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) update release.

Symptoms

Assume that you install Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) or Microsoft SQL Server 2012 Reporting Services (SSRS 2012) on a computer. When you try to render or export a report that contains a Tablix control from Windows Internet Explorer, you receive the following error message intermittently:
Server Error in '/Reports' Application.
--------------------------------------------------------------------------------
An internal error occurred on the report server. See the error log for more details. (rsInternalError)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Reporting.WebForms.ReportServerException: An internal error occurred on the report server. See the error log for more details. (rsInternalError)

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Additionally, the following error message is logged in Reporting services error log:
library!ReportServer_0-2!122c!04/03/2012-23:48:06:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Invalid offset for item. ReferenceID: ffffffffffffff5d, Offset: -163, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.;

library!ReportServer_0-2!122c!04/03/2012-23:49:40:: i INFO: Exception InternalCatalogException dumped to: C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\Logfiles flags= AllMemory, AllThreads, SendToWatson

Note You receive these error messages if the Tablix control meets the following conditions:
  • The Tablix control has at least one row group and at least one column group.
  • There are at least 100 instances of the column group.
  • The cell at the intersection of the row and column group contains a nested Tablix control, a chart, or other data regions.

Resolution

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2723749 Cumulative update package 3 for SQL Server 2012
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 2012 fix release. Microsoft recommends 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. 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:
2720425 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
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:
2730301 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative update package 7 for SQL Server 2008 R2 SP1

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 R2 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2703282 Cumulative update package 6 for SQL Server 2008 R2 SP1
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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released
Microsoft SQL Server 2008 R2 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 R2 Service Pack 1 hotfix to an installation of SQL Server 2008 R2 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 2707015 - Last Review: August 29, 2012 - Revision: 7.0
Applies to
  • Microsoft SQL Server 2008 R2 Reporting Services
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2707015

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com