FIX: Error message when you use SQL Server 2005 Report Manager to try to run a linked report: "An internal catalog exception has occurred" (917070)

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: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.