SQL Server Q&A

Symptoms
On server that is running Microsoft SQL Server 2008 Reporting Services, you generate a report from a custom data extension data source. To do this, you use the “Asynchronous Processing = True” setting in the connection string property.When you run the report, the report server stops responding.
Resolution
This issue occurs because the System.Data.SQLclient namespace does not support asynchronous processing in any hosted common language runtime (CLR) environment. Because Reporting Services hosts the CLR within the Reporting Services process, the asynchronous call always fails.
Note The System.Data.SQLclient namespace is the SQL Server .Net Data Provider.

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 occurredWhen 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.
Resolution
The problem occurs because the report properties are not replicated to the linked reports.