Microsoft KB Archive/917070

= FIX: Error message when you use SQL Server 2005 Report Manager to try to run a linked report: &quot;An internal catalog exception has occurred&quot; =

Article ID: 917070

Article Last Modified on 7/26/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Developer Edition

-



Bug #: 617 (SQL Hotfix)

Bug #: 450540 (SQLBUDT)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SYMPTOMS
When you use SQL Server 2005 Report Manager to try to run a linked report, you receive an error message that resembles the following:

An Internal Catalog Exception has occurred

When you examine the Reporting Services log files after you receive the error message, you may notice the following call stack: w3wp!library!1!1/27/2006-13:10:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., un-named assertion fired for component processing; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. w3wp!processing!7!1/27/2006-13:10:27:: a ASSERT: Assertion failed! Call stack: Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.Initialize(Stream stream) Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader..ctor(Stream stream) Microsoft.ReportingServices.ReportProcessing.ChunkManager+DataChunkReader..ctor(DataSet dataSet, Int32 reportUniqueName, UInt32 subreportLevel, GetReportChunk getChunkCallback) This problem occurs when the following conditions are true:
 * The linked report contains the user dependency. For example, you use the expression User!UserID for a field.
 * The linked report has an execution property that is set to use snapshots.



CAUSE
The problem occurs because the report properties are not replicated to the linked reports.



RESOLUTION
To resolve this problem, install the cumulative hotfix package (build 2153) for SQL Server 2005 that is discussed in Microsoft Knowledge Base article 918222. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

918222 Cumulative hotfix package (build 2153) for SQL Server 2005 is available



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, 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

Keywords: kbbug kbfix kbtshoot kbqfe kbpubtypekc KB917070

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.