October 9, 2017 at 6:22 pm
Sue_H - Monday, October 9, 2017 12:57 PMDo you get the error with any other websites and IE 11? Have you tried another browser to see if you get the same error?
Also, Thom asked about the Reporting Services log and if there are any related errors in there. The log you posted above is just from Reporting Services starting up so it isn't going to provide any information. If you go to Report Manager, to the Report and run the report, that would log any potential errors for the report.Sue
HI Sue,
Please find below the errors that i've found in the logs:
library!WindowsService_0!39c!10/09/2017-16:00:29:: i INFO: Call to CleanBatch() ends
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: WriteCallback(): failed to write in write callback.
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x0000000000A4FE80.
rshost!rshost!1b00!10/09/2017-16:01:40:: e ERROR: HttpPipelineCallback::SendResponse(): failed async writing response.
rshost!rshost!1b00!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x0000000000A4FE80.
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: WriteCallback(): failed to write in write callback.
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000B35A3F0.
rshost!rshost!1110!10/09/2017-16:01:40:: e ERROR: HttpPipelineCallback::SendResponse(): failed async writing response.
rshost!rshost!1110!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000B35A3F0.
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: WriteCallback(): failed to write in write callback.
rshost!rshost!d34!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000B35A690.
rshost!rshost!1520!10/09/2017-16:01:40:: e ERROR: HttpPipelineCallback::SendResponse(): failed async writing response.
rshost!rshost!1520!10/09/2017-16:01:40:: e ERROR: Failed with win32 error 0x03E3, pipeline=0x000000000B35A690.
httpruntime!ReportManager_0-1!1110!10/09/2017-16:01:40:: 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)
httpruntime!ReportManager_0-1!1b00!10/09/2017-16:01:40:: 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)
httpruntime!ReportManager_0-1!1520!10/09/2017-16:01:40:: 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-1!1b00!10/09/2017-16:01:40:: 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_RSNATIVE_0-1-131520300288786121. ---> 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 ---;
library!ReportManager_0-1!1110!10/09/2017-16:01:40:: 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_RSNATIVE_0-1-131520300288786121. ---> 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 ---;
library!ReportManager_0-1!1520!10/09/2017-16:01:40:: 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_RSNATIVE_0-1-131520300288786121. ---> 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)
October 10, 2017 at 1:50 am
Those don't appear to to reference the report your running anywhere. I would expect to see run time requests in the log, however, I can't even see any.
Apart from editing and saving the file while SSRS was running, and the absence of relevant log data, I've run out of ideas though I'm afraid. Any and all of the steps I stated should have resovevd the problem (which makes me thing one hasn't been applied).
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply