Hi All, I have a report which has around 10k records. I am getting Timed out error sometimes when I try to export data to excel. But, strangely this happens most of the time. But, sometimes, i am able to download the excel. I have even tried download .csv..its works fine (i just tried couple of times).. I have even tried setting the Do not timeout report execution = true and even tried the other option of increasing the report execution timeout. Is there any other option in Configuration files that I need to make the changes? Kindly help me. Thanks, Prawin Prawin

Please provide more details about your environment. The version of Reporting Services, with build numberOperating System on Server. Did you check reporting services log files? they are located here: Report Server Service Trace Log, please share across the errors from the log files. Chaitanya( Twitter | Blogs ) Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles. This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Chaitanya, Thanks for your reply. I am not exactly sure of the OS at this point of time.. It should be Windows 2008 server. And, we are using SQL Server 2008 R2..But, I am not sure of the build number... will checjk them and get back to you on the exact details. However, In fact, I am able to download the excel file from one of the server on the production server network.. but, not from normal workstation on the interent! But, sometimes i am able to export it to excel bu sometime i am not.. I will check the log files and get back to you! Thanks, PrawinPrawin

Another thing is that I can see a record in reportserver.executionlog2 table when I try to export data to excel.. Somehow, I am unalbe to download it..It gives me "Operation timeout"..I am unalbe to understand if it is a SSRS error or ASP.NET error.. I tried to increase the RequestLength and Executiontimeout in the web.config file loacted in the ReportServer folder! Thanks, PrawinPrawin

Hello, Is the report appearing? And while exporting only the issue occurs? If so try executing the query in SSMS and see what happens is it working well there. I mean the query you are using for getting the data

Yes..The report is working fine...Even the excel export is working if there around 6k records...the problem is only when it is around 8k to 9k records..However, sometimes even the export works fine for 8k records...but sometimes its not working fine!Prawin

I kept an eye on my logs...Here are the exception details.. webserver!ReportServer_0-36!5c0!03/11/2012-05:40:19:: i INFO: Processed report. Report='/MyReportName', Stream='' rshost!rshost!5dc!03/11/2012-05:40:37:: e ERROR: WriteCallback(): failed to write in write callback. rshost!rshost!5dc!03/11/2012-05:40:37:: e ERROR: Failed with win32 error 0x04D4, pipeline=0x000000000036CFA0. rshost!rshost!5c0!03/11/2012-05:40:37:: e ERROR: HttPipelineCallback::SendEntityBody(): failed async writing entity body. rshost!rshost!5c0!03/11/2012-05:40:37:: e ERROR: Failed with win32 error 0x04D4, pipeline=0x000000000036CFA0. httpruntime!ReportServer_0-36!5c0!03/11/2012-05:40:37:: e ERROR: Failed in BaseWorkerRequest::SendHttpResponse(bool), exception=System.Runtime.InteropServices.COMException (0x800704D4): The network connection was aborted by the local system. (Exception from HRESULT: 0x800704D4) at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.SendEntityBody(Void* chunks, UInt16 chunkCount, Boolean finalWrite, Boolean closeConn) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) library!ReportServer_0-36!5c0!03/11/2012-05:40:37:: 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 ReportServer_MSSQLSERVER_0-36-129759100654729115. ---> System.Runtime.InteropServices.COMException (0x800704D4): The network connection was aborted by the local system. (Exception from HRESULT: 0x800704D4) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush) --- End of inner exception stack trace ---; Prawin

Hi Prawin Were you able to find a solution to your problem? I'm receiving a similar error from render an SSRS report using Reporting Service web service Thanks

No.. We did not find any solution for that... we are NOT always getting that error...50% of the times we are getting that error....seems it is a problem with resources! but not sure... we are planning to update the server configuration and so stopped our research! will let you if we find any solution!Prawin

what version of excel is the user/client is using?Think out of the box

Excel 2010. But, I don't think this is an issue with the client version!Prawin

Hello everyone, It seems that we have a similar problem. Our configuration: Report server 2008 integrated in SharePoint 2007 on a windows server 2008.. We have a report that doesn't work when it has to return to much data (when the render time is to long). We get an error in Sharepoint saying 'Unexpected error' when I make a big selection. However, this doesn't happen when I use the same selection for this report in the SSRS native mode. The report will render for a couple of minutes then but wil return a result. Here is the reportserver log for when I execute the report from the Sharepoint integrated mode: Report='/Financien/rsrapporten/budget.rdl', Stream='' library!WindowsService_11!1a5c!05/31/2012-10:36:10:: i INFO: Call to CleanBatch() library!WindowsService_11!1a5c!05/31/2012-10:36:10:: i INFO: Cleaned 0 batch records, 0 policies, 4 sessions, 0 cache entries, 4 snapshots, 32 chunks, 0 running jobs, 0 persisted streams, 657 segments, 657 segment mappings. library!WindowsService_11!1a5c!05/31/2012-10:36:10:: i INFO: Call to CleanBatch() ends rshost!rshost!64c!05/31/2012-10:38:52:: e ERROR: WriteCallback(): failed to write in write callback. rshost!rshost!64c!05/31/2012-10:38:52:: e ERROR: Failed with win32 error 0x04D4, pipeline=0x000000000E20BD90. rshost!rshost!1bc0!05/31/2012-10:38:52:: e ERROR: HttpPipelineCallback::SendResponse(): failed async writing response. rshost!rshost!1bc0!05/31/2012-10:38:52:: e ERROR: Failed with win32 error 0x04D4, pipeline=0x000000000E20BD90. httpruntime!ReportServer_0-5!1bc0!05/31/2012-10:38:52:: e ERROR: Failed in BaseWorkerRequest::SendHttpResponse(bool), exception=System.Runtime.InteropServices.COMException (0x800704D4): The network connection was aborted by the local system. (Exception from HRESULT: 0x800704D4) at Microsoft.ReportingServices.HostingInterfaces.IRsHttpPipeline.SendResponse(Void* response, Boolean finalWrite, Boolean closeConn) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) library!ReportServer_0-5!1bc0!05/31/2012-10:38:52:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_MSSQLSERVER_0-5-129829192776500067. , RsWorkerRequest::FlushResponse.; Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeInternalException: An internal or system error occurred in the HTTP Runtime object for application domain ReportServer_MSSQLSERVER_0-5-129829192776500067. ---> System.Runtime.InteropServices.COMException (0x800704D4): The network connection was aborted by the local system. (Exception from HRESULT: 0x800704D4) at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush) at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush) The report is set in Sharepoint to not give a timeout. I even increased the timeout in the web.config for the sharepoint farm.. Does anybody have any idea how to fix this?? BTW, I prefer not to let my users work with the report in native mode (this is a workaround, it should work within Sharepoint!). Regards, Ron Verhoeven