Geek asks and answers

Filling logs: with error message with remote host

We are trying to understand what is happening with this error, is it just disconnecting users from the site?

System.Web.HttpException  An error occurred while communicating with the remote host. The error code is 0x800703E3.  
System.Runtime.InteropServices.COMException  The I/O operation has been aborted because of either a thread exit or an application request. 
(Exception from HRESULT: 0x800703E3)  StackTrace:    
at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)     
at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()    
at System.Web.HttpResponse.Flush(Boolean finalFlush)     
at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size)     
at System.Web.Mvc.FileStreamResult.WriteFile(HttpResponseBase response)     
at System.Web.Mvc.ControllerActionInvoker.<>c__DisplayClass1c <InvokeActionResultWithFilters>b__19()     
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilter(IResultFilter filter, ResultExecutingContext preContext, Func`1 continuation)    
at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)     
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)     
at System.Web.Mvc.Controller.ExecuteCore()    
at System.Web.Mvc.ControllerBase.Execute(RequestContext requestContext)    
at System.Web.Mvc.MvcHandler.<>c__DisplayClass6.<>c__DisplayClassb.<BeginProcessRequest>b__5()   
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass1.<MakeVoidDelegate>b__0()  
at System.Web.Mvc.MvcHandler.<>c__DisplayClasse.<EndProcessRequest>b__d() 
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()    
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
+5
source share
1 answer

Yes, this error occurs when the connection with the user is lost. Perhaps they closed the browser or were disconnected (or the request failed or was canceled ).

The answer to a similar question recommends checking Response.IsClientConnected before calling Flash ()

You may not even need to explicitly call Flush ()

+3
source

More articles:


All Articles