Microsoft KB Archive/945600

= FIX: You receive an exception error message when you try to display a Reporting Services report on a server that uses the AMD Cool'n'Quiet technology =

Article ID: 945600

Article Last Modified on 12/11/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Reporting Services

-



Bug: #50002053 (SQL Hotfix)



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
Consider the following scenario in Microsoft SQL Server 2005 Reporting Services (SSRS):
 * You use the AMD Cool'n'Quiet technology on the server.
 * You try to display a report.

In this scenario, you receive the following exception error message:

w3wp!library!6!09/11/2007-10:35:36:: i INFO: Call to RenderFirst( '/Site/Database

Usage' )

w3wp!processing!6!09/11/2007-10:35:36:: a ASSERT: Assertion failed! Call stack:

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.UpdateTimingInformatio

n(RunningJobContext jobContext, Int64 totalDurationMs, Int64

reportDataRetrievalDurationMs, Int64 reportRenderingDurationMs)

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderin

gExtension renderer, DateTime executionTimeStamp, GetReportChunk

getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc,

CreateReportChunk cacheDataCallback, Boolean& dataCached)

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime

executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext

pc, RenderingContext rc)

Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext

reportContext, ItemProperties properties, ParameterInfoCollection

effectiveParameters, Guid reportId, ClientRequest session, String description,

ReportSnapshot intermediateSnapshot, DataSourceInfoCollection

thisReportDataSources, Boolean cachingRequested, Boolean isLinkedReport, Warning[]&

warnings, ReportSnapshot& resultSnapshotData, DateTime& executionDateTime,

RuntimeDataSourceInfoCollection& alldataSources, UserProfileState& usedUserProfile)

Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemCont

ext reportContext, ClientRequest session, Warning[]& warnings,

ParameterInfoCollection& effectiveParameters)

Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext

reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection&

effectiveParameters, String[]& secondaryStreamNames)

Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute

Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper

Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService

rs, CatalogItemContext reportContext, ClientRequest session, JobType type,

Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]&

secondaryStreamNames)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResp

onseStreamFactory streamFactory)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOperation(S

treamedOperation operation)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType

itemType)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.ProcessRequest(HttpCo

ntext context)

System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExec

utionStep.Execute

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&

completedSynchronously)

System.Web.HttpApplication.ResumeSteps(Exception error)

System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpCont

ext context, AsyncCallback cb, Object extraData)

System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)

System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)

System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)

w3wp!library!6!09/11/2007-10:35:36:: 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.

The exception is being thrown by

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.UpdateTimingInformatio

n.

This procedure is in Reporting Services\ReportServer\bin\Microsoft.ReportingServices.ProcessingCore.dll.



RESOLUTION
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 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 2005 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



WORKAROUND
To work around this problem, use the method that is described in the &quot;Resolution&quot; section of Microsoft Knowledge Base article 895980. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

895980 Programs that use the QueryPerformanceCounter function may perform poorly in Windows Server 2003 and in Windows XP



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
After you apply this hotfix, a &quot;-1&quot; is logged in the report server execution log. Additionally, the following information is logged in the Reporting Services log file:

Timestamp values retrieved from current CPU are not synchronized with other CPUs.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

