Microsoft or Experts, We recently upgraded our Reporting Server to SSRS 2008 R2 and now our report server box is maxed at 100% CPU. The server is running Windows 2008 64-bit, at 4 gig ram I have checked the report server logs and noticed that a lot of reports are throwing exception errors when they are trying to render. But the big question is in the event viewer, ASP.NET 2.0.50727 is throwing a lot of warning messages dealing with the following error: Event code: 3005 Event message: An unhandled exception has occurred. Event time: 6/22/2010 9:02:16 AM Event time (UTC): 6/22/2010 1:02:16 PM Event ID: 8ea64fa30c534f049df16cf16fee1336 Event sequence: 1600 Event occurrence: 3 Event detail code: 0 Application information: Application domain: ReportServer_MSSQLSERVER_0-1-129216551832223187 Trust level: RosettaSrv Application Virtual Path: /ReportServer Application Path: C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\ Machine name: MSREPORTER Process information: Process ID: 2036 Process name: ReportingServicesService.exe Account name: NT AUTHORITY\SYSTEM Exception information: Exception type: ThreadAbortException Exception message: Thread was being aborted. Request information: Request URL: http://msreporter/ReportServer/Reserved.ReportServer? An unhandled exception has occurred.fPROD An unhandled exception has occurred.freports An unhandled exception has occurred.fFieldMgmt An unhandled exception has occurred.fRoleup_Client_Branch_NotesPending&rs:SessionID=403llt35hpbwi3452mu4icml&rs:command=Render&rs:Format=HTML4.0&rc:HTMLFragment=true&rc:Section=1&rc:StreamRoot= An unhandled exception has occurred.fPortalAn unhandled exception has occurred.fNET An unhandled exception has occurred.fReportingServices An unhandled exception has occurred.fReserved.ReportViewerWebControl.axd6/22/2010 9:02:16 AMfReportSession6/22/2010 9:02:16 AMd403llt35hpbwi3452mu4icmlNT AUTHORITY\SYSTEMControlID6/22/2010 9:02:16 AMdc0e10f03118a49c7810c4b83ea43e7e5NT AUTHORITY\SYSTEMCulture6/22/2010 9:02:16 AMd1033NT AUTHORITY\SYSTEMUICulture6/22/2010 9:02:16 AMd1033NT AUTHORITY\SYSTEMReportStack6/22/2010 9:02:16 AMd1NT AUTHORITY\SYSTEMOpType6/22/2010 9:02:16 AMdReportImageNT AUTHORITY\SYSTEMStreamID6/22/2010 9:02:16 AMd&rc:ResourceStreamRoot= An unhandled exception has occurred.fPortal An unhandled exception has occurred.fNET An unhandled exception has occurred.fReportingServices An unhandled exception has occurred.fReserved.ReportViewerWebControl.axd6/22/2010 9:02:16 AMfReportSession6/22/2010 9:02:16 AMd403llt35hpbwi3452mu4icmlNT AUTHORITY\SYSTEMControlID6/22/2010 9:02:16 AMdc0e10f03118a49c7810c4b83ea43e7e5NT AUTHORITY\SYSTEMCulture6/22/2010 9:02:16 AMd1033NT AUTHORITY\SYSTEMUICulture6/22/2010 9:02:16 AMd1033NT AUTHORITY\SYSTEMReportStack6/22/2010 9:02:16 AMd1NT AUTHORITY\SYSTEMOpType6/22/2010 9:02:16 AMdReportImageNT AUTHORITY\SYSTEMResourceStreamID6/22/2010 9:02:16 AMd&rc:ActionScript=ClientReportc0e10f03118a49c7810c4b83ea43e7e5.ActionHandler&rc:StyleStream=true&rc:LinkTarget=_top&rc:UserAgent=Mozilla An unhandled exception has occurred.f4.0+(compatible6/22/2010 9:02:16 AMb+MSIE+7.06/22/2010 9:02:16 AMb+Windows+NT+5.16/22/2010 9:02:16 AMb+InfoPath.16/22/2010 9:02:16 AMb+.NET+CLR+1.1.43226/22/2010 9:02:16 AMb+.NET+CLR+2.0.507276/22/2010 9:02:16 AMb+.NET+CLR+3.0.4506.21526/22/2010 9:02:16 AMb+.NET+CLR+3.5.30729)&rc:Toolbar=false&rs:ErrorResponseAsXml=true&rs:AllowNewSessions=false Request path: /ReportServer/Reserved.ReportServer User host address: 10.72.132.132 User: YORK\MSREPORTER Is authenticated: True Authentication Type: NEGOTIATE Thread account name: NT AUTHORITY\SYSTEM Thread information: Thread ID: 4 Thread account name: NT AUTHORITY\SYSTEM Is impersonating: False Stack trace: at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)

Here is one of the report errors from the SQL report server log.... library!ReportServer_0-1!8d4!06/22/2010-08:57:57:: i INFO: RenderForNewSession('/PROD/reports/FieldMgmt/Roleup_Client_Branch_NotesPending') processing!ReportServer_0-1!2c8!06/22/2010-09:02:04:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.OnDemandReportRendering.ReportItem.get_Top() at Microsoft.ReportingServices.Rendering.SPBProcessing.ItemSizes.Update(ReportItem reportItem) at Microsoft.ReportingServices.Rendering.SPBProcessing.PageContext.PageContextCommon.GetSharedItemSizesElement(ReportItem reportItem, Boolean isPadded) at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox..ctor(TextBox source, PageContext pageContext, Boolean createForRepeat) at Microsoft.ReportingServices.Rendering.SPBProcessing.PageItem.Create(ReportItem source, PageContext pageContext, Boolean tablixCellParent, Boolean createForRepeat) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddDetailCell(TablixCell cellDef, Int32 colIndex, Double cellColDefWidth, Double cellCellDefHeight, Boolean fullOnPage, Boolean collect, Boolean& partialItem) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateDetailCell(Tablix tablix, TablixMember colMemberParent, Int32 colGridIndex, TablixContext context) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateColumnMemberChildren(Tablix tablix, TablixMember colMemberParent, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, TablixContext context, Boolean createDetail, LevelInfo& parentLevelInfo) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateColumnMemberChildren(Tablix tablix, TablixMember colMemberParent, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, TablixContext context, Boolean createDetail, LevelInfo& parentLevelInfo) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateTablixItems(Tablix tablix, TablixContext context) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double& parentPageHeight, Interactivity interactivity) at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportBody.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double& parentPageHeight, Interactivity interactivity) at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportSection.CalculatePage(RPLWriter rplWriter, Int32 page, Int32 totalPages, Int32 regionPageNumber, Int32 regionTotalPages, Boolean firstSectionOnPage, Boolean lastSection, Interactivity interactivity, Double heightToBeUsed, PageItemHelper& lastBodyInfo, Boolean& delayedHeader, Boolean& delayedFooter, Boolean& lastSectionOnPage) at Microsoft.ReportingServices.Rendering.SPBProcessing.Report.NextPage(RPLWriter rplWriter, ReportSectionHelper& lastPageInfo, Int32 page, Int32 totalPages, Interactivity interactivity, Boolean hasPaginationChunk) at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.PaginateReport(Int32 startPage, Int32 endPage) at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.UpdateRenderProperties(Hashtable& renderProperties) at Microsoft.ReportingServices.Rendering.HtmlRenderer.ServerRenderer.UpdateRenderProperties(Hashtable& renderProperties) at Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension.InternalRender(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.Rendering.HtmlRenderer.RenderingExtensionBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension newRenderer, DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory metaDataChunkFactory, IChunkFactory yukonCompiledDefinition) --- End of inner exception stack trace ---; library!ReportServer_0-1!2c8!06/22/2010-09:02:13:: w WARN: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.OnDemandReportRendering.ReportItem.get_Top() at Microsoft.ReportingServices.Rendering.SPBProcessing.ItemSizes.Update(ReportItem reportItem) at Microsoft.ReportingServices.Rendering.SPBProcessing.PageContext.PageContextCommon.GetSharedItemSizesElement(ReportItem reportItem, Boolean isPadded) at Microsoft.ReportingServices.Rendering.SPBProcessing.TextBox..ctor(TextBox source, PageContext pageContext, Boolean createForRepeat) at Microsoft.ReportingServices.Rendering.SPBProcessing.PageItem.Create(ReportItem source, PageContext pageContext, Boolean tablixCellParent, Boolean createForRepeat) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.TablixContext.AddDetailCell(TablixCell cellDef, Int32 colIndex, Double cellColDefWidth, Double cellCellDefHeight, Boolean fullOnPage, Boolean collect, Boolean& partialItem) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateDetailCell(Tablix tablix, TablixMember colMemberParent, Int32 colGridIndex, TablixContext context) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateColumnMemberChildren(Tablix tablix, TablixMember colMemberParent, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, TablixContext context, Boolean createDetail, LevelInfo& parentLevelInfo) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateColumnMemberChildren(Tablix tablix, TablixMember colMemberParent, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, TablixContext context, Boolean createDetail, LevelInfo& parentLevelInfo) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateRowMemberChildren(Tablix tablix, TablixMember rowMemberParent, InnerToggleState parentToggleState, Int32 defTreeLevel, Boolean parentBorderHeader, Int32 parentRowIndex, Int32 parentColIndex, Int32 level, TablixContext context, Boolean& advanceRow, LevelInfo& parentLevelInfo, List`1& ignoreTotals, Boolean keepTogether) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CreateTablixItems(Tablix tablix, TablixContext context) at Microsoft.ReportingServices.Rendering.SPBProcessing.Tablix.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double& parentPageHeight, Interactivity interactivity) at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportBody.CalculatePage(RPLWriter rplWriter, PageItemHelper lastPageInfo, PageContext pageContext, PageItem[] siblings, RepeatWithItem[] repeatWithItems, Double parentTopInPage, Double& parentPageHeight, Interactivity interactivity) at Microsoft.ReportingServices.Rendering.SPBProcessing.ReportSection.CalculatePage(RPLWriter rplWriter, Int32 page, Int32 totalPages, Int32 regionPageNumber, Int32 regionTotalPages, Boolean firstSectionOnPage, Boolean lastSection, Interactivity interactivity, Double heightToBeUsed, PageItemHelper& lastBodyInfo, Boolean& delayedHeader, Boolean& delayedFooter, Boolean& lastSectionOnPage) at Microsoft.ReportingServices.Rendering.SPBProcessing.Report.NextPage(RPLWriter rplWriter, ReportSectionHelper& lastPageInfo, Int32 page, Int32 totalPages, Interactivity interactivity, Boolean hasPaginationChunk) at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.PaginateReport(Int32 startPage, Int32 endPage) at Microsoft.ReportingServices.Rendering.SPBProcessing.SPBProcessing.UpdateRenderProperties(Hashtable& renderProperties) at Microsoft.ReportingServices.Rendering.HtmlRenderer.ServerRenderer.UpdateRenderProperties(Hashtable& renderProperties) at Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension.InternalRender(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.Rendering.HtmlRenderer.RenderingExtensionBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension newRenderer, DateTime executionTimeStamp, ProcessingContext pc, RenderingContext rc, IChunkFactory metaDataChunkFactory, IChunkFactory yukonCompiledDefinition) --- End of inner exception stack trace ---

This has not been resolved yet. The CPU stays at 99%, then memory goes well over 3 gig, then server re-sets reporting Services, a SQL Dump is created and then the report server is back down to proper utilization. As soon as a few reports are kicked off, the report server CPU climbs back to 99% and this continues....

Hi, Try to apply the following hotfix at http://support.microsoft.com/kb/981355/en-us on the machine and add more hardware to support this reporting service. thanks, Jerry

Jerry, Thanks for the reply, I will instruct our DBA to install CU1 for SSRS 2008 R2 and get back to this thread with an update. Turns out there was an older RDL file that was causing the report server to max out CPU time everytime you ran it. When you ran this older RDL file it would spike the CPU in 25% intervals. I tested this by running this report 4 times and every time it ran, the CPU went to 25,50,75,100 until the report server performed a SQL dump. Now since i have re-written this older report, the report server does not spike in CPU time, but the memory now does not seem to be releasing... so one part is fixed, now I am concerned about the memory (its well over 1 gig now) Any other ideas? Once we install the CU1 I will keep you posted. Thanks Jerry! - Art

Jerry, The installation of R2 did not fix the issue we are having. The CPU issue has slowed down due to a rewrite of a report, however the memory is not releasing when a report is completed. The only way the memory releases is when the server performs a DUMP and re-sets.

Jerry, this might be funny but it had to deal with the following: After a lengthy investigation into this, it turns out to be the following: 1.) The reports in question were reports that were developed in SSRS 2000, that were ported to SSRS 2005 and were then promoted to SSRS 2008 when we converted our database to 2008, etc.. Based on some posts dealing with conversion/upgrade issues the rdl files did not convert correctly to SSRS 2008 R1/R2 when they were promoted to the SSRS servers. a. It had to deal with a custom color that was used for the detail row of our reports. Once this was set to use a default SSRS 2008 color, like LightGreen, the report was deployed to the sever and then it could run. i. We were using a HEX# for this and this failed on the server, once updated to use light green, it worked. ii. =IIf(RowNumber(Nothing) Mod 2, "White", "#C1FFC1") (FAILED), change to: 1. =IIf(RowNumber(Nothing) Mod 2, "White", "LightGreen") (WORKED) 2.) Also, with some reports, another developer would copy/paste the textboxes on the RDL file if they had to deal with the same expression. a. Meaning if you had 2 groups on the report, say AMOUNT, if you dragged and dropped AMOUNT to be used for 2 groups SSRS would create the 2 textboxes as AMOUNT_1 and AMOUNT_2 ( as VB would with the array group). i. Well 2005’s SSRS server processed those correctly, especially when you exported to a PDF file. ii. HOWEVER with SSRS 2008 both R1/R2, if you did the same thing, the report would render to the screen but if you exported to PDF, you got the infamous Unhandled exception error with ASP.NET 2.0, etc…. 1. So the fix is you have to change the textboxes that use the old VB array syntax, AMOUNT[0], AMOUNT[1] or AMOUNT_1, AMOUNT_2, etc. to just be unique textboxes (just copy the expression from the textbox, delete the textbox(which creates a new textbox reference) and then paste the expression in the formula) 2. Bingo, the report now will work/render with no problems… So following these steps above fixed our SSRS 2008 R1/R2 report problems and we are on our way.. To bad it took us over 2 weeks and lots of man hours to figure this out…..

Well the CPU problem seems to be fixed where we could upgrade the reports, however we are now having a problem with the memory no longer releasing... It just seems to climb during the day and then when the server reseaches a threshhold, it resets itself and then the process continues... I wonder if there is a way to resolve this memory leak...

Hi, I have just downloaded the free version of SQL Server 2008 complete with the management studio and all the other bits onto my windows 7 32 bit pc. I have just started teaching myself how to use it, creating a couple of databases, writing queries, views and database procedures. as part of my education. To my knowledge I have never written a report or tried to use the reporting service, and yet several times, when I have not been using SQL server at all, I have found that the reporting service is hogging 100% of my pc's CPU (both cores of a dual core intel chipset.). It only happens intermittently and it is easy enough to stop the service so that the problem goes away, but does anyone know why this would be happening? Many thanks in advance for your help. Alan Watson

I am also seeing this behavior. I.e. start the service, do not access any SSRS resources and after 5 minutes the ReportingServicesService is consuming 4Gb RAM an 100% on 4 cpusAndrew Wiles - www.it-workplace.com - MDX made simple

I have opened a connect issue here with MS... https://connect.microsoft.com/SQLServer/feedback/details/569742/reportingservicesservice-exe-at-100-cpu-utilization?wa=wsignin1.0

It turns out that our particular problem was associated with SharePoint indexing. I am gussing that the SharePoint index crawler was opening up SSRS Reports to index the content. We have fixed the problem in the short term by changing the indexing schedule from one every 5 minutes to once a day at midnight. We are developing a solution at the moment so this is acceptable for our current need we will however need to review if this is acceptable when we make the solution live.Andrew Wiles - www.it-workplace.com - MDX made simple

We are not using SharePoint and can still reproduce this... We get either 100% utilization or high memory on the server (anywhere between 1-2 gig) and then a dump happens, looks like the memory does not release and I am starting to think it might be because 90% of the reports came from SQL 2005=>2008 There are some rpeorts that came from SQL 2000=>2005=>2008 and once I had updated those reports by removing any of the _1 or _x fields and replacing the textboxes, the reports seem to have dropped the CPU when completed but the memory still held (using report viewer 2008 in our application) So we had to roll back to our R1 server and that seems to be stable now but we really would like to move to R2...

Well, I gotta reply to this one... We have a production 64bit Server with 16CPU cores and 128GB ram with Sharepoint2010 and the whole MSBI R2 suite. We are testing out ReportBuilder3.0 and SSRS, and by now experienced more than few times a 99% CPU maxout due to the Reporting Services. We have created only a small set of simple reports which are supposed to run in 2-3 seconds but at some random point in time the server CPU maxes out! We were forced to stop the reporting services service and find a solution online. If we dont we will have a go for another reporting solution.. Oh yes, we don't have old reports from SSRS2005, and our reports are only drafts which only a few people can run so far..

No, I have not heard of any solution.... We had to abandon the install due to time constraints... Ideally we should have built the R2 box from scratch which could have possible prevented this...

Hello, Did you find the solution? I am facing same issue on our Production Server. ReportService take more CPU. I have to forcefully Stop Reporting Service every time to resolve this issue.