Small report executes endless
Hi, SSRS version 2008 R2. I have a report which can run for some time, but only returns 1 row. When the report has to run for less than 5 minutes, it works fine. But when the query takes more than 5 minutes, the report executes endless. The message 'Loading... Cancel' stays busy in my window. The report is finished. I have added some logging in my stored proc, so I know it is finished. Also in the reportserver log I find the report is finished: 12/07/2011-14:38:37:: i INFO: RenderForNewSession('/Customer/StandardData') 12/07/2011-14:43:50:: i INFO: Processed report. Report='/Customer/StandardData', Stream='' I would think there must be some configuration value, but I can't find which one. Thanks for any help.
December 7th, 2011 10:18am

It's easy to reproduce. Just create this stored procedure: CREATE PROCEDURE [dbo].[Testreport] AS BEGIN SET NOCOUNT ON WAITFOR delay '00:05:05' SELECT 'Test ' AS Col1, 'keep running' AS col2 END Create a report which returns the results of this stored procedure. When the DELAY is lower than 5 minutes, it works fine, I get the result. When the delay is greater than 5 minutes, it keeps running.
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2011 11:22am

Check report server timneout. I remember the default value to be 5. I might be wrong
December 8th, 2011 11:29am

Hi erde, Thanks for the question and Kiranmayee’s reply. Please check the time-out property settings from below approaches. 1. The Time out in Report Manager. You had set it. It helps us to control the maximum time of report execution, if timeout, though the report haven’t been represented, it also stop executing. 2. The Time out in Data Source. Please check it. It helps us to control the maximum time of creating one connection to the Data Source server, if timeout, though the connection haven’t been created, it will stop. 3. The Time out time in Data Set. Please check it. It helps us to control the maximum time of querying data from the Data Source server, if timeout, though the querying haven’t been finished, it will stop executing. 4. The Time out in application to connect to the Report Server. You had set it by previous script. It helps us to control the maximum time of keeping ping connection from application to Report Server, if timeout, it stops the ping connection. 5. The Time out in application to keep the application available. Please check it. You can double-click the Web.config file in your application project then check it. For more information, please see: HttpSessionState.Timeout Property. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2011 9:10pm

Thanks for your reply Kiranmayee and Sharp Wang. On the report server I have following timeout settings: Session timeout = 600 System Report timeout=43200 External Images timeout = 600 Edit session timeout = 7200. 1. Report manager - site settings: Limit report processing = 1800 seconds 2. Data source connect timeout = 15, Load balancing timeout = 0. Don't find any other timeouts. 3. Data set timeout = 0 4. Application = ie. But the arrow continues to run. After clicking 'Cancel', it is possible to rerun or do something else. What do you mean with 'You had set it by previous script? 5. HttpSessionState timeout. Where to check/change with ie? The web.config in the ReportManager dir contains <sessionState mode="InProc" cookieless="false" timeout="20" />. I can't find anything about 5 minutes/300 seconds. Thanks, Eric.
December 9th, 2011 3:56am

Session Timeout is the default value and no issues to change it. When we set DataSet timeout, Application timeout happens. thats what Sharp Wang meant. Did you try setting the report to subscription and executing it, to see if works or not? If it works for Subscription, then, please let us know
Free Windows Admin Tool Kit Click here and download it now
December 12th, 2011 4:44pm

Hi Kiranmayee, Different subscriptions tried, and they all work.
December 15th, 2011 4:21am

Thanks for the reply, Kiranmayee. Based on the subscription testing, it seems like when running the report in report server directly, the issue doesn't occur. Does this issue happens in specify clients or some other conditions? Best Regards, Sharp WangPlease remember to mark the replies as answers if they help you and unmark them if they provide no help.
Free Windows Admin Tool Kit Click here and download it now
January 2nd, 2012 4:06am

Check for server timeout.
January 2nd, 2012 11:15am

PA-Singh: Which server timeout? In a previous reply I have given all defined timeouts I have found. Sharp Wing: It happens on all clients. And with different reports. Eric.
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2012 5:30am

Hi, I have new information about this problem. When the report is executed with IE on the server itself, the report returns fine. When the report is executed on a client via internet, then it keeps running. After the query is executed, the browser stays with the 'Loading...' icon spinning, and we have the following error in the RS log: webserver!ReportServer_0-4!884!07/10/2012-09:28:28:: i INFO: Processed report. Report='/Customer/StandardData' rshost!rshost!135c!07/10/2012-09:28:28:: e ERROR: WriteCallback(): failed to write in write callback. rshost!rshost!135c!07/10/2012-09:28:28:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000016DA40. rshost!rshost!f14!07/10/2012-09:28:28:: e ERROR: HttpPipelineCallback::SendResponse(): failed async writing response. rshost!rshost!f14!07/10/2012-09:28:28:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000016DA40. httpruntime!ReportManager_0-3!f14!07/10/2012-09:28:28:: e ERROR: Failed in BaseWorkerRequest::SendHttpResponse(bool), exception=System.Runtime.InteropServices.COMException (0x800703E3): The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3) at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.SendResponse(Void* response, Boolean finalWrite, Boolean closeConn) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) library!ReportManager_0-3!f14!07/10/2012-09:28:28:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: RsWorkerRequest::FlushResponse., Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportManager_MSSQLSERVER_0-3-129860539775661442. ---> System.Runtime.InteropServices.COMException (0x800703E3): The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush) --- End of inner exception stack trace ---; This occurs for any report with a query which takes more than 5 minutes to return the resultset. Thanks for any help.
July 10th, 2012 5:47am

Hi, It may be the case of parameter sniffing have a look on the below link http://www.sqlservercentral.com/blogs/practicalsqldba/2012/06/25/sql-server-parameter-sniffing/ Hope this will help you !!! Sanjeewan
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2012 5:59am

Sanjeewan, No it has nothing to do with the stored procedure and parameter sniffing (I know this). It has to do with connection over the internet or not. It only happens with clients which connect over the internet. Eric.
July 10th, 2012 6:10am

Hi There Thanks for your posting. In Reporting Services, there are three processing phases when we view a report: data retrieval, report process and report rendering. To find out how much time is spent on each processing phase when we view a report on the report manager we can get this information from the report server execution log via the SSMS. Please go to your report server database and run this query. select * from ExecutionLog3 order by TimeStart DESC I would also recommend you please also run a profiler and put a trace and see what is going on your sql server while the report is not responding that might give you some clue. please also have a look Report Server Execution Log and the ExecutionLog3 View ExecutionLog2 View - Analyzing and Optimizing Reports I hope this will help Many thanks Syed Qazafi Anjum
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2012 7:20am

This are the results from ExecutionLog3, the first one returned the report from a localm client, the second one was via internet and stays running. TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount 2012-07-10 07:57:34.540 2012-07-10 08:07:24.613 589706 142 175 Live rsSuccess 289400 1652 2012-07-10 08:14:40.010 2012-07-10 08:24:21.677 581295 136 182 Live rsSuccess 289400 1652
July 10th, 2012 7:33am

It is as we have a timeout. Because it only appears with internet sessions, is it possible it has something to do with the http session and the 'keep-alive' setting? How can I change this? Can I set this for the report manager sessions?
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 3:15am

Hi Erde, I've got exactly the same problem with more-then-5min reports and all symptoms you mentioned i can see on my environment (5 min delay, [The I/O operation has been aborted because of either a thread exit or an application request] error etc.) I guessed if the timeout is put by some intermediate software (proxy-servers for example) and cannot be fixed by SSRS settings. My colleagues suggested using https protocol as it has to keep connection alive. In my case it worked out perfectly Regards, Sergey
August 6th, 2012 3:47am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics