An error occurred rendering the report. Accessing the report server URL caused an error. The operation has timed out

(0) Share

Report

Posted on by ford_sopris

1,229

I have a client that is on R2 CU7 that is trying to print a large number of checks and when the "Generate Payment" and send the job to a redirected printer, we are getting "An error occurred rendering the report. Accessing the report server URL caused an error. The operation has timed out". This happens after about 3 minutes. We have increased every timeout I could find but I have not ever seen a "3 minute" timeout yet. I have copied the DB over to an All in One DEV system so it is running on a different SQL server SSRS server, etc. If they break up the checks and run them separately, they print just fine.

I think this is the full error out of the SSRS logs:

library!ReportServer_0-3!87c!11/06/2015-09:32:20:: i INFO: RenderForNewSession('/DynamicsAX/Cheque_US.Report')
webserver!ReportServer_0-3!d94!11/06/2015-09:32:21:: i INFO: Processed report. Report='/DynamicsAX/Cheque_US.Report', Stream=''
webserver!ReportServer_0-3!d84!11/06/2015-09:34:28:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeClientDisconnectionException: A client has disconnected from the Report Server Web service application domain ReportServer_MSSQLSERVER_0-3-130913003526545575. No corrective action is required. An error code has been submitted to ASP.NET to release the connection. The error code is 80070040. ---> System.Runtime.InteropServices.COMException (0x80070040): The specified network name is no longer available. (Exception from HRESULT: 0x80070040)
   at ReportingServicesHttpRuntime.BaseWorkerRequest.SendHttpResponse(Boolean finalFlush)
   at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush)
   --- End of inner exception stack trace ---
   at ReportingServicesHttpRuntime.BaseWorkerRequest.FilterAndThrowException(Exception e, String message)
   at ReportingServicesHttpRuntime.RsWorkerRequest.FlushResponse(Boolean finalFlush)
   at System.Web.HttpResponse.Flush(Boolean finalFlush)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.HttpResponseWrapper.<>c__DisplayClass1.<ReturnResponseBody>b__0()
   at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass1.<Run>b__0(Object state)
   at System.Security.SecurityContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state)
   at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody callback)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.HttpResponseWrapper.ReturnResponseBody(RSStream result, HttpResponse resp)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.HttpResponseWrapper.WriteRSStream(RSStream stream)
   at Microsoft.ReportingServices.Library.StreamRequestHandler.RenderReport(SessionfulClientRequest sessionManager)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(SessionfulClientRequest sessionManager)
   at Microsoft.ReportingServices.Library.StreamRequestHandler.PerformStreamedOperation(StreamedOperation operation)
   at Microsoft.ReportingServices.Library.StreamRequestHandler.RenderItem(ItemType itemType)
   at Microsoft.ReportingServices.Library.StreamRequestHandler.ExecuteCommand()
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
library!ReportServer_0-3!d84!11/06/2015-09:34:28:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: The request has been aborted., Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeException: An error occurred in the HTTP Runtime object for application domain ReportServer_MSSQLSERVER_0-3-130913003526545575. Most likely, the HTTP request contains an unsupported verb or invalid syntax. ---> System.Web.HttpException: Server cannot set status after HTTP headers have been sent.
   at System.Web.HttpResponse.set_StatusCode(Int32 value)
   at Microsoft.ReportingServices.Common.ErrorResponseWriter.WriteError()
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.WriteErrorResponse(Int32 code, String shortHttpDescription, Exception exception, String optionalMessage, Boolean errorResponseAsXml)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.WriteErrorResponse(Int32 code, String shortHttpDescription, Exception exception, Boolean errorResponseAsXml)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderError(Int32 code, String shortHttpDescription, Exception e)
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
   at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
   --- End of inner exception stack trace ---;

Any thoughts?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

I have a similar problem with my one of the client, however it was not early as 3 min for timeout. What I would suggest instead of printing checks directly to printer, print it to screen and you will never face timeout issues.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Did you get a resolution to this issue yet? We are facing an exactly similar issue and am wondering if there is any easy fix to the problem. The issue with printing to the screen directly is that when we print cheques in batches of 100 or 200, opening the pdf and printing it individually would become a nightmare.

Was this reply helpful? Yes No
ford_sopris 1,229 on at

Like (0)

Report

Not that I know of. I believe they ended up splitting up the print job and printing so many at a time.

Was this reply helpful? Yes No
Brandon Wiese 17,788 on at

Like (0)

Report

The error message

"The specified network name is no longer available. (Exception from HRESULT: 0x80070040)"

suggests that the problem is most likely a network issue. I would suggest switching RDP to TCP only (no UDP), and avoid using a redirected printer if at all possible.

Was this reply helpful? Yes No
jacqy george2 50 on at

Like (0)

Report

Hello,

I am also facing a similar issue with a client generating a large number of checks. This happens in one company only and not the other, so the issue seems odd. Both companies are using the same check printer. TempDB has enough drive space. Timeouts have been increased. Seems to be a connection issue of some sort. Any suggestions on how to remedy? Printing to screen is not an option.

Thank you!

processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: e ERROR: An exception has occurred in data set 'Cheque_USDS'. Details: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed.
processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ...
processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: e ERROR: Data source 'AutoGen__ReportDataProvider': An error has occurred. Details: System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSet.ProcessConcurrent(Object threadSet)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.ExecuteSequentialDataSets()
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.Process(Boolean fromOdp)
processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: e ERROR: Data source 'AutoGen__ReportDataProvider': Rolling the transaction back.
processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: e ERROR: An exception has occurred in data source 'AutoGen__ReportDataProvider'. Details: System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSet.ProcessConcurrent(Object threadSet)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.ExecuteSequentialDataSets()
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.Process(Boolean fromOdp)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.ProcessConcurrent(Object threadSet)
processing!ReportServer_0-16!13b8!05/19/2016-14:44:33:: i INFO: Some other thread has already aborted processing.
library!ReportServer_0-16!13b8!05/19/2016-14:44:33:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
library!ReportServer_0-16!13b8!05/19/2016-14:44:33:: w WARN: Transaction rollback was not executed connection is invalid
library!ReportServer_0-16!13b8!05/19/2016-14:44:33:: w WARN: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.InvalidOperationException: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.
library!ReportServer_0-16!13b8!05/19/2016-14:44:35:: i INFO: Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. ---> System.InvalidOperationException: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.
runningjobs!ReportServer_0-16!13b8!05/19/2016-14:44:35:: e ERROR: error in thread function: System.Threading.ThreadAbortException: Thread was being aborted.
   at Microsoft.ReportingServices.Library.AsyncExecution.AsyncStartMain(Object state)
   at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
   at Microsoft.ReportingServices.Diagnostics.ThreadWorkItem.FullSafeThreadPoolCallback(Object param)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

jacqy george2 did you find a solution to this issue. I am facing the same issue but only in one company

Was this reply helpful? Yes No