We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

The I/O operation has been aborted because of either a thread exit or an application request [Answered]RSS

65 replies

Last post Oct 31, 2012 03:53 AM by runningfree

  • The I/O operation has been aborted because of either a thread exit or an application request

    Jun 10, 2008 03:46 AM|Jason Hill|LINK

    Hi, 

    We are in the process of moving our application across to a new installation of Win Server 2008 Datacenter. During testing, we are seeing a couple of errors come through when doing rapid simultaneous ajax postbacks:

    The I/O operation has been aborted because of either a thread exit or an application request

    The specified network name is no longer available

    Does anyone know what is causing this and how we should be handling this? This was never a problem on our IIS6 machine so it must be something that has changed in IIS7.

    Thanks,

    Jason

  • Rovastar Rovastar

    5495 Posts

    MVP

    Moderator

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 10, 2008 06:07 AM|Rovastar|LINK

    Where are these errors occuring?

    http layer? https?

    iis layer?

    event viewer?

    Are you running a virtual machine?

    Are you connecting to a database? (if you are check the DB logs to see more info)

    Looked around a bit and maybe it is a known issue see here:

     http://forums.asp.net/t/1248261.aspx

    Troubleshoot IIS in style
    https://www.leansentry.com/
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 10, 2008 06:48 AM|Jason Hill|LINK

    Thanks for the response. 

    Some answers to your questions:

    • <div mce_keep="true">The errors are getting reported back to the asp.net application and being notified to the admin. It is just http and not https but I am not sure which layer they are occuring in. </div>
    • <div mce_keep="true">The event viewer is showing the same exception that I have listed.</div>
    • <div mce_keep="true">It is not a virtual machine.</div>
    • <div mce_keep="true">We are connecting to a SQL Server 2005 database and I can't see anything in the logs that point to a problem there.</div>

    The UI allows for multiple ajax async postbacks to be fired by the user changing some checkboxes and other form elements on the page. If I make a lot of rapid changes, which fires of simultaneous requests and probably even queues up a couple, then I start getting these errors through. The application does not seem to be adversely affected and contues to operate as expected without the user seeing these errors. It does result in these errors getting logged and email to us though so we would really like to fix the problem.

    That post you linked to mentions the client being disconnected...do you think that applies in this case, i.e. the initial ajax async postback gets disconnected because we have fired off subsequent ones? This was never a problem in IIS6 but maybe it is something to do with the pipeline changes in IIS7?

    The first workaround in that post is too laborious because there would be lots of places where we have this type of async postback. I don't understand the 2nd workaround. Isn't this just going to discard all application errors that get raised? We would not want this but just want to ignore either of the 2 that I mentioned in my original post. Several months for a fix seems pretty cr*p too!

    Here is the full stack trace of one of the errors:

    Exception of type 'System.Web.HttpUnhandledException' was thrown.

    at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.broadband_refine_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

    The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)

    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Web.Util.Misc.ThrowIfFailedHr(Int32 hresult) at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size) at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.get_Form() at System.Web.HttpRequest.get_HasForm() at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) at System.Web.UI.Page.DeterminePostBackMode() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 10, 2008 05:12 PM|tmarq|LINK

    Unfortunately, in integrated mode on Vista RTM, Vista SP1, and Windows Server 2008, if the HTTP client is disconnected, or disconnects, when ASP.NET reads the entity body or flushes the response, ASP.NET converts the HRESULT from IIS to an exception and throws it.  The actual HRESULT can vary depending on the IIS function that fails, but here are a few common ones:

     

    0x800703E3 "The I/O operation has been aborted because of either a thread exit or an application request."

     

    0x800704CD "An operation was attempted on a nonexistent network connection."

     

    0x80070040 "The specified network name is no longer available."

     

    0x80070001 "Incorrect function."

     

    0x80070006 "The handle is invalid."

     

    This is fixed in .NET Framework v2.0 SP2.  With the fix you will not see any exceptions when the client is disconnected, or disconnects, while ASP.NET reads the entity body.  This is scheduled to release this summer (I believe in approximately six weeks) along with .NET Framework v3.5 SP1.  

     

    Thanks,

    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 11, 2008 05:30 PM|Jason Hill|LINK

    Thanks Thomas. Do you know if there is a hotfix available for this?

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 11, 2008 05:48 PM|tmarq|LINK

    There is no hotfix for this, but please feel free to contact me via my blog at http://blogs.msdn.com/tmarq/contact.aspx and I will put you in touch with product support.  If I'm correct about the release date of v2.0 SP2, then it would be difficult to create, test, and sign-off on a hotfix in less time than the release of v2.0 SP2.

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 22, 2008 12:03 AM|Jason Hill|LINK

    Big thanks to Thomas for the awesome customer service and providing a private build which contained the fix for this problem.

    Jason

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 13, 2008 12:39 PM|tmarq|LINK

    Good news!  .NET Framework 3.5 Service Pack 1 released on Monday August 11, and can be downloaded at http://www.microsoft.com/downloads/details.aspx?FamilyId=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en.  It includes an update to the .NET Framework 2.0 binaries that will fix the issue described in this forum post.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Dec 15, 2008 10:35 AM|Alexey.UA|LINK

    Hi Thomas,

    You have stated that "with the fix you will not see any exceptions when the client is disconnected while ASP.NET reads the entity body."

    And what about flushing the response? Would it be throwing an exception in both Integrated and Classic modes in the same case?

    Following exceptions can be thrown when client is disconnected while flushing, but Classic mode one seems to be somehow intermittent:

    An error occurred while communicating with the remote host. The error code is 0x80070057.:   
    at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
    at System.Web.HttpResponse.Flush(Boolean finalFlush)
    at System.Web.HttpResponse.Flush()
    at ASP.default_aspx.Page_Load(Object sender, EventArgs e)

    The remote host closed the connection. The error code is 0x80070057.:
    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.HttpResponse.Flush()
    at ASP.default_aspx.Page_Load(Object sender, EventArgs e)
  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Dec 15, 2008 11:53 AM|tmarq|LINK

    In both Classic and Integrated mode, ASP.NET will throw an exception if the client closes the connection during or before an explicit flush.  An explicit flush means that someone called HttpResponse.Flush.  This has been the behavior in classic mode for a long time, and so integrated mode does the same.

    Thank you,
    Thomas

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Apr 30, 2009 11:04 AM|tmarq|LINK

    This is about as direct as it gets.  I work at Microsoft, and made the change to fix the issue described in this post.

    Thank you,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 24, 2009 03:51 PM|vishalpatole|LINK

    Hi Thomas,

    First of all thanks for all valuable information shared here.

    On Windows 2008 - 64 bit IIS7 server; I still see an error discussed in this forum (given below):

    System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Web.HttpException: An error occurred while communicating with the remote host. The error code is 0x80070057.
    at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async)
       at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
       at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
       at System.Web.HttpResponse.Flush(Boolean finalFlush)
       at System.Web.HttpResponse.Flush()
       at System.Web.UI.Control.OnLoad(EventArgs e)
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    IIS app pool is configured for "Classic" and .Net Framework 3.5 Service Pack 1 is already available on the server. Error is not reported by end user so I believe it is mainly happening when client closes the connection. Changing app pool to "Integrated" will not solve the issue, is it correct? Could you please help me to diagnosis this issue.

     

    Thanks

    Vishal

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 14, 2009 02:13 PM|tmarq|LINK

    Hi Vishal,

    You've found a known bug in Windows Server 2008.  The bug is in IHttpConnection::IsConnected, which ocassionally returns TRUE when it should return FALSE.  The bug is WinSE 275030, and you can contact Microsoft Product Support and request a fix.

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 15, 2009 11:29 AM|jpbaker22|LINK

    I contacted Microsoft Support and mentioned "WinSE 275030" and they said it was for exchange 5.5?

    Do you have any more details on how to acuire the hotfix?

     Thanks. 

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 15, 2009 11:37 AM|tmarq|LINK

    It is "Windows SE 275030".

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 03, 2009 05:01 PM|MattDuguid|LINK

    We are seeing a similar issue with a recent move to Windows 2008 x64 Web Edition and IIS 7.0.

    The servers are running .NET 3.5, .NET 3.5 SP1 and KB959209 (.NET SP1 update) and KB967535 (fixes a known request blocking issue which under certain circumstances caues the request queue to halt).

    The number of errors are not huge compared to the number of page impressions we go through daily but something we'd still like to clean up.

    The problem 

    During ***some*** file uploads after a ***few seconds*** we get the following 500 error (located via failed request tracing),

    Error = The I/O operation has been aborted because of either a thread exit or an application request. (0x800703e3)

    Error Code = 2147943395

    Which produces the following exception,

    Exception: [System.Web.HttpException] Request timed out.

    Research

    http://forums.iis.net/p/1149787/1871363.aspx
    Some articles suggest this is a known issue and fixed with the application of .NET SP1 (we have this applied). Could it be the bug has been reintroduced through the application of the additional service packs, rather unlikely but not impossible as I have seen this happen before with other products.

    http://forums.asp.net/t/1248261.aspx
    Some articles suggest that the client is simply disconnecting their session which causes an exception at the server and is not being handled correctly. There are some code workarounds but the concensus seems to be that these are just covering up the issue and not fixing the root cause.

    Some articles suggest the execution timeout is being exceeded, in our case this is 90 seconds and in the traces I have seen to date the issue can happen in less than 15 seconds.

    Ideas

    If you have experienced the same issue and have possible ideas for solutions please let us know.

    0x800703E3 2147943395 .net sp1 [System.Web.HttpException] Request timed out file upload The I/O operation has been aborted because of either a thread exit or an application request

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 11, 2009 03:32 PM|mdurnwald|LINK

    Thomas,

    Who can we contact to get this fix?  We have the same problem.

    Thanks,

    Mike

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 09:57 AM|jb|LINK

    We are seeing this error too, but our circumstances are a little differenct.  

    100-200 times a day we fail to get a complete post body of a request (I/O operation aborted).

    The real problem for us is that IIS locks the session object of the user who made that request. Further requests from that user are blocked until the original request times out (2 min default) causing our user to be blocked from the site and in the past causing many hits to our session database.

    I can see why msft might lock the session and start the aspx processing before reading the entire request, but it seems non-optimal/like a bug to us right now.

     Is there anything we can do to delay session locking or move reading the data off the wire earlier? Any advice is appreciated.

    We are looking at EnableSessionState=False or EnableSessionState=ReadOnly, but this will mean major changes to our application.

     Configuration/Usage:
       IIS 7, Windows Server 2008, .Net Framework 3.5 SP1 + KB953595, 958484
       10,000 non-anonymous users a day
        1.1 Million page views/ajax requests a day

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 11:01 AM|tmarq|LINK

    I'm sure that if you call back the same thing won't happen twice.  Here's more information about the bug: 

    Database:  Windows SE
    Bug ID:  275030
    Title: IHttpConnection::IsConnected Returns Invalid Results
    Path:   Windows SE\LongHorn\Server Technologies\IIS\App Server Engine\Web Core

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 11:25 AM|jb|LINK

     So, just to confirm. You are saying that if IIS was informed that the connection was dropped, it would unlock the session more quickly? That makes sense.

     The test client I wrote that reproduces this did not close the connection, but that may not be real world behavior.

    I'll call support, get the fix and see if it helps.

    I'll also sniff the network and see if I can correlate the network traffic with the logs and tell whether the connections are closed when we stop getting data (or if they are open just not sending for some reason).

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 11:58 AM|jb|LINK

    I called support and unfortunately all they were able to find was a hotfix for kb275030 (which doesn't seem to be the same as bug 275030). It is in Czech. Web searches seem to indicate something about exchange or windows 2000 sp2.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 12:49 PM|anilr|LINK

    The hotfix for the bug that tmarq mentions has not yet been built or released.

    That said, I don't think your problem is at all related to the bug that tmarq mentioned (which only results in a spurious event log message/exception) - in your case, it seems like you are reading client request entity after the session has been locked and this is timing out after 2 mins and during those 2 mins, all other requests using that session are blocked - the only way to fix that would be to read the request entity before the OnAcquireRequestState event using a HttpModule rather than in your handler/aspx page like you are currently doing.  Also, like you mentioned, you may be able to disable auto session locking and then manually lock it in your code after reading the request entity.

    Anil Ruia
    Software Design Engineer
    IIS Core Server
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 01:13 PM|jb|LINK

     Your understanding is exactly correct. tmarq emailed me and he too was concerned that the fix wouldn't fix this problem.

    I think I'm going to ask our developers to try reading the post body (or do something that causes it to be read) in the Application_OnBeginRequest handler in global.asax. I'm hoping this is early enough in the pipeline to be before OnAcquireRequestState. It looks like it should be early enough from the "Professional IIS7" book. I would like to avoid a custom HTTPModule just because we haven't done one before.

    I hadn't thought of getting AcquireRequestState because it is so early in the process. Thanks for pushing me in that direction.

     Let me know if you see a flaw in this plan. I'll let you/everyone know if it works.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 27, 2009 04:21 PM|jb|LINK

    We have decided not to read the post body in the OnBeginRequest event. This would probably slow down all requests a tiny bit as it would wait for the post body before starting the pipeline (instead of starting processing while the post comes in).

    Instead we think we are going to set EnableSessionState=ReadOnly (which will be a hack at first). We will actually still be writing to the session on these pages and this will only work with inproc session storage. We haven't implemented and tested this fully yet, but it appears to work. Eventually we will confine our session updates to a few pages and mark those pages as session updateable pages. Then the "readonly" setting won't be a hack, the pages really will be readonly.

     

    Coming from another architecture into this one, this all seems a bit odd. The session object in other environments is not threadsafe just like the application object isn't in asp.net. This gives the developer the chance to screw themselves up, but it also lets them deal with (avoid) issues like this.

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Sep 12, 2009 08:50 PM|whitesites|LINK

     I was getting this error about 50 times a day on a website that does about 35K impressions daily.  Something I read on another site was to make sure any web control that doesn't need to postback has enableviewstate set to false.  This will greatly reduce the size of your viewstate.  Since doing this I am only get 15 errors of this kind each day. So it helped by was not the silver bullet I was looking for. 

    I have created a post on my blog discussing this,

    fixing The remote host closed the connection. The error code is 0x80070057

     

    If anyone has any suggestions let me know.  All my other websites are running fine except this one.  Seems to be some problem with .IIS7WorkerRequest.ExplicitFlush()

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Sep 17, 2009 12:35 AM|MattDuguid|LINK

    We set enableviewstate to false at site level via the web.config and still get this error. I believe you may have a slightly different problem to us as your error is 0x80070057 and ours is 0x800703e3.

    We sre still trying to track this down...

    The I/O operation has been aborted because of either a thread exit or an application request. (0x800703e3)

    ErrorCode 2147943395

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 01:38 AM|gunjan.gandhi|LINK

    Hi All,

    I had read all the comments on this blog, Even i having same error with the following enviorment.

    --> Window server 2008 64bit, .Net 3.5 with SP1, IIS7

    In my web application, it give me error when following line excute.

    Response.Flush()

    Response.End()

    Even in some blog i had read to remove flush statment but it didn't work.  even end statement give me same error(An error occurred while communicating with the remote host. The error code is 0x80070057).

    So, If any one having idea related to this issue. Please please inform me.

    I required it ASAP.

    Thanks all in advance.

    Gunjan  

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 01:51 AM|whitesites|LINK

     Let me take a wild guess,

    You are getting this error and your W3WP.exe is really big

    Disable the viewstate on your label controls.

    Once I did this the problem web away.

    I wrote a blog entry on some possible solutions

    w3wp.exe using too much memory and resources

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 02:51 AM|gunjan.gandhi|LINK

    hi whitesites,

    Thanks for your response, But let me tell you one thing, i had check my W3WP process and it is not so much big which close the session.

    Enve i had check that befor executing flush command IsCilentConnect property give me true value and after executing flush statment it give me false value.

    This code is perfectlly run under Window server 2003, .net 3.5sp1, iis6.

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 02:58 AM|whitesites|LINK

     What is your script trying to do?

    Why are you explicitly using flush?

    Did you check your Label Controls?

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 03:16 AM|gunjan.gandhi|LINK

    Let me clear one thing, in my web application i had create one file as per the user requirment i pass it to user. even i had created one demo application and find the same error at flush statment. In this application i does not use any lable only one button is used. please find my aspx code blow

    ASPX CODE

    <%@ Page Language="VB" AutoEventWireup="false" CodeFile="Default.aspx.vb" Inherits="_Default" %>

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">

    <head runat="server">

    <title></title> </head>

    <body>

    <form id="form1" runat="server">

    <div>

     

    </div>

    <asp:Button ID="Button1" runat="server" Text="Button" EnableViewState="false" />

    </form> </body>

    </html>

    ASPX.VB CODE

    Imports System.IO

    Partial Class _Default

    Inherits System.Web.UI.Page

    Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click Dim SendFile As FileInfo

    Dim line_1 As Integer

    Dim FileNameArr() As String

    Dim FileNameWithPath As String

    Dim Response_1 As HttpResponse

    Try

    Response_1 = Me.Response

    FileNameWithPath = "c:\Test.xls"

    SendFile = New FileInfo(FileNameWithPath)

    Response_1.ClearContent()

    Response_1.ClearHeaders()

    Response_1.AppendHeader(
    "Content-Disposition:", "attachment; filename =" + SendFile.Name)Response_1.AppendHeader("Content-Length:", SendFile.Length.ToString())

     

    Response_1.ContentType = "application/vnd.ms-excel"

    Response_1.TransmitFile(FileNameWithPath)

    Response_1.Flush()

    Response_1.End()

    Catch ex As Exception

    If Not TypeOf ex Is System.Threading.ThreadAbortException Then

    Throw New Exception(ex.Message + vbCrLf + "Error occured while Exporting File " + line_1.ToString())

    End If

    Finally

    End Try

    End Sub

    End Class

     You can see that application does not use lable. Even though it will provide me same error.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 03:26 AM|whitesites|LINK

     That is alot of code for something relatively simple

    Response.Clear();
    Response.ContentType = "image/jpeg";
    Response.WriteFile(location);
    Response.End();

     I use this to dynamically write a JPG image.

    location = "path to image relative to my applications root"

    Maybe it will give you some ideas for how you can simplify you code.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 22, 2009 05:31 AM|gunjan.gandhi|LINK

    Thanks whitesites,

    For kind support, I had found the victime of my code. When i had commented my following line

                Response_1.AppendHeader("Content-Length:", SendFile.Length.ToString())

    And all works.

    But at the same time when i am going to check Headers.count property of Response object then it give me error that IIS Integrity mode required. I does not know how to check this issue.

    Thanks once again.

    Gunjan 

     

     

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 27, 2009 06:44 AM|jonesri|LINK

    tmarq

    Database:  Windows SE
    Bug ID:  275030
    Title: IHttpConnection::IsConnected Returns Invalid Results
    Path:   Windows SE\LongHorn\Server Technologies\IIS\App Server Engine\Web Core

     

    Hi Thomas,

     Do you have an update on this bug?  We are experiencing this problem on our production server at the moment.

    Thanks

    Richard Jones

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 27, 2009 10:17 AM|whitesites|LINK

     Post some source code.

    Something that seemed to solve the problem for me was to remove the explicit flush statements, and simplify my code.

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 30, 2009 12:37 PM|tmarq|LINK

    I've received several enquiries about the status of Windows SE Bug # 275030, but I do not work in that department and do not know its current status.  To learn more about the fix and how you can obtain it, please contact a Microsoft Support Professional via the "Contact Us" links at http://support.microsoft.com.  Again, as posted earlier, the bug information is:

    Database:  Windows SE
    Bug ID:  275030
    Title: IHttpConnection::IsConnected Returns Invalid Results
    Path:   Windows SE\LongHorn\Server Technologies\IIS\App Server Engine\Web Core

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 30, 2009 07:15 PM|MattDuguid|LINK

    FYI - some stack traces of the error in case this helps shed more light on the issue. I've performed failed request traces during image uploads and watched them bomb out after only a few thousands bytes have been transfered (and these were small files and well within configured limits). We have seen it in two very seperate applications and given other people outside our site have assume its not restircted to us. Again interested in any ideas people have about this one.

    Source: System.Web
    Exception: [System.Web.HttpException] An error occurred while communicating with the remote host. The error code is 0x80070001.
    Method: Void RaiseCommunicationError(Int32, Boolean)
    Stack:
       at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityBody(Byte[] buffer, Int32 size)
       at System.Web.HttpRequest.GetEntireRawContent()
       at System.Web.HttpRequest.GetMultipartContent()
       at System.Web.HttpRequest.FillInFormCollection()
       at System.Web.HttpRequest.get_Form()
       at System.Web.HttpRequest.get_HasForm()
       at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
       at System.Web.UI.Page.DeterminePostBackMode()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Source:
    Exception: [System.Runtime.InteropServices.COMException] Incorrect function. (Exception from HRESULT: 0x80070001)
    Method:
    Stack:


    Source: System.Web
    Exception: [System.Web.HttpException] An error occurred while communicating with the remote host. The error code is 0x800703E3.
    Method: Void RaiseCommunicationError(Int32, Boolean)
    Stack:
       at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size)
       at System.Web.Hosting.IIS7WorkerRequest.ReadEntityBody(Byte[] buffer, Int32 size)
       at System.Web.HttpRequest.GetEntireRawContent()
       at System.Web.HttpRequest.GetMultipartContent()
       at System.Web.HttpRequest.FillInFormCollection()
       at System.Web.HttpRequest.get_Form()
       at System.Web.HttpRequest.get_HasForm()
       at System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull)
       at System.Web.UI.Page.DeterminePostBackMode()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Source:
    Exception: [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)
    Method:
    Stack:

    IIS7 0x800703E3 0x80070001 file upload The I/O operation has been aborted because of either a thread exit or an application request Incorrect function An error occurred while communicating with the remote host

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Dec 04, 2009 10:53 AM|brian-murphy-booth|LINK

    .

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Apr 22, 2010 10:48 PM|akshayns|LINK

    May be this hotfix will be useful -

    FIX: You receive a COMException exception when you run ASP.NET Web applications in IIS 7.0 on a computer that is running Windows Vista or Windows Server 2008

    http://support.microsoft.com/kb/977453

     

  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Apr 22, 2010 11:16 PM|tmarq|LINK

    Yes, http://support.microsoft.com/kb/977453 is the fix for the issue I described earlier.  It is finally available.  Sorry for the wait.

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 19, 2010 12:15 PM|JohnCC|LINK

    I'm getting the first error that Matt Duguid reported ( [System.Web.HttpException] An error occurred while communicating with the remote host. The error code is 0x80070001. ) about 3 or 4 times a day on a low traffic website. The site is on a shared hosting environment so I'm very restricted in terms of what I can do to debug it. However, do we know from this discussion whether this error is related to the other one, the topic subject? I have not seen the 0x800803E3 error at all. Has anyone found a solution to this 0x80070001 error? The only exact match I could find other than this thread was http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/698e2b2b-af59-4848-b041-4fbb11c5bb6b which implies it's an issue with virtualization.
  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jul 19, 2010 12:40 PM|tmarq|LINK

    John,

    The error code varies, and it does not matter if it is 0x80070001 or 0x800803E3.  Please ask the administrator of your shared hosting environment to install the fix described in my earlier posts.  The link is http://support.microsoft.com/kb/977453.

    The error code varies because IIS is failing at different function calls when the client disconnects, and the error codes returned by these functions are not all the same.  To determine if the client disconnected, ASP.NET calls IHttpConnection::IsConnected.  This function returns true when it should be returning false, and ASP.NET throws the HttpException that you're seeing.  The problem with IHttpConnection::IsConnected is fixed in KB 977453.  Once that is installed, ASP.NET will stop throwing the HttpException. 

    If the client is disconnected, then it really doesn't matter if an exception is thrown or not, as long as the process does not crash.  In your case, the exception is eventually caught by ASP.NET, so the process does not crash.  It is however annoying and confusing to see these exceptions.  Classic mode simply consumes them, so you never see them, and that is what integrated mode is supposed to do to, for backward compatibility.  You just need to install KB 977453.  Sorry about the hassle.

    Thanks,
    Thomas 

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Aug 16, 2010 12:36 AM|luker459|LINK

    Sorry, i replied before reading the end of the thread. If i could delete this post i would, but i can't see an option anywhere.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 03, 2010 05:08 AM|softlion|LINK

    Hi, i get this exception for the first time in my app since 6 months. The only patch i installed is the security fix for ASP.NET crypting vulnerability released last week. I'm on Windows 2008 R2 and ASP.NET MVC 4. 500 503 Service unavailable baseEx: 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) exceptionMessage: An error occurred while communicating with the remote host. The error code is 0x800703E3. exceptionMessage-1: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3) exceptionStack: at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect) at System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(Byte[] buffer, Int32 offset, Int32 size) at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.get_Form() at System.Web.Mvc.HttpRequestExtensions.GetHttpMethodOverride(HttpRequestBase request) at System.Web.Mvc.AcceptVerbsAttribute.IsValidForRequest(ControllerContext controllerContext, MethodInfo methodInfo) at System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate) at System.Web.Mvc.ActionMethodSelector.RunSelectionFilters(ControllerContext controllerContext, List`1 methodInfos) at System.Web.Mvc.ReflectedControllerDescriptor.FindAction(ControllerContext controllerContext, String actionName) at System.Web.Mvc.ControllerActionInvoker.FindAction(ControllerContext controllerContext, ControllerDescriptor controllerDescriptor, String actionName) at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName) at System.Web.Mvc.Controller.ExecuteCore() at System.Web.Mvc.MvcHandler.<>c__DisplayClass8.b__4() at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass1.b__0() at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) exceptionStack-1: (null) exceptionType: System.Web.HttpException exceptionType-1: System.Runtime.InteropServices.COMException

    ASP.NET 4

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 03, 2010 03:57 PM|MattDuguid|LINK

    Check the versions of files in the patch (http://support.microsoft.com/kb/977453) are still the same on the affected machine or if they have been updated as a result of applying the fix. Do you have another server without the patch you can also use as a reference?

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 19, 2010 06:49 PM|arvestal|LINK

    Hello, I'm getting this error as well. I also have the patch installed. This is not happening in my test environment, but it is happening in production.  win server 2008, iis7 64bit.

    ErrorMessage: The remote host closed the connection. The error code is 0x80070057.

    ViewFileHandler.ashx::201010131034ARV RecipeId: 12  Stack::   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.HttpResponse.Flush()    at System.Web.HttpResponse.End()    at ViewFileHandler.ProcessRequest(HttpContext context) in d:\Web\projects\recipes\ViewFileHandler.ashx:line 133

    code: (it blows up on the binarywrite)

    public void ProcessRequest (HttpContext context)
    {
        string id = context.Server.UrlDecode(context.Request.QueryString["recipeId"].ToString());
       
        MemoryStream ms = GetRecipeStream(id);
        byte[] recipe = ms.GetBuffer();
       
        try
        {
            context.Response.Clear();
            context.Response.Buffer = false;
            context.Response.ContentType = "Application/pdf";
            context.Response.BinaryWrite(recipe);
        }
        catch (System.Threading.ThreadAbortException ex)
        {
        }
        catch (System.Runtime.InteropServices.COMException ex)
        {
        }
        catch (Exception ex)
        {
            if (IsLoggerOn)
            {
                List<string> data = new List<string>();
                data.Add("ViewFileHandler.ashx::201010131034ARV");
                data.Add("RecipeId: " + id);

                Logger log = new Logger("ProcessRequest", data, ex);
                log.LogException();
            }
        }
    }

    public bool IsReusable
    {
        get {
            return false;
        }
    }

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 08, 2010 01:02 PM|Amrendrakr|LINK

    Hi Thomas, application hosted on IIS7 and windows 2008, getting error: Need help
    Event message: An unhandled exception has occurred. Event time: 11/8/2010 8:05:39 AM Event time (UTC): 11/8/2010 1:05:39 PM Event ID: fa73224bf8414063b63a032bee97519b Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2/ROOT/Portal-1-129336122316272500 Trust level: Full Application Virtual Path: /Portal Application Path: C:\Customers\Portal\ Process information: Process ID: 2328 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: HttpException Exception message: An error occurred while communicating with the remote host. The error code is 0x800704CD. Request information: Request URL: https://localhost:443/Portal/User/AppLogin.aspx?ReturnUrl=An unhandled exception has occurred.fportalAn unhandled exception has occurred.fdefault.aspx Request path: /Portal/User/AppLogin.aspx User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 6 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async) at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal) at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush) at System.Web.HttpResponse.Flush(Boolean finalFlush) at System.Web.HttpResponse.Flush() at System.Web.HttpResponse.End() at System.Web.HttpResponse.Redirect(String url, Boolean endResponse) at System.Web.HttpResponse.Redirect(String url) at CorrespondentPortalWebApp.Global.Session_Start(Object sender, EventArgs e) at System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) at System.Web.SessionState.SessionStateModule.CompleteAcquireState() at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 08, 2010 01:26 PM|tmarq|LINK

    Amrendrakr,

    I'm fairly certain the client has disconnected.  Without http://support.microsoft.com/kb/977453 installed, the error message will be "An error occurred while communicating with the remote host." or "The remote host closed the connection".  With http://support.microsoft.com/kb/977453 installed, the error message will be "The remote host closed the connection" if the client did in fact disconnect.

    If the client is disconnecting, you're always going to get the error you displayed in your post.  You could avoid it by not calling Redirect(url) but instead calling Redirect(url, false) and Context.ApplicationInstance.CompleteRequest() as described at http://blogs.msdn.com/b/tmarq/archive/2009/06/25/correct-use-of-system-web-httpresponse-redirect.aspx.

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 08, 2010 02:28 PM|Amrendrakr|LINK

    Thanks for quick reply... Client was conneted to application, even I tried my self, appliction was not responding and Event log error generated, once restart the IIS error gone. Don't know why it happened. ......... Exception message: An error occurred while communicating with the remote host. The error code is 0x800704CD. I did not tried : 977453, since its related to COMException, I am getting: Exception information: Exception type: HttpException Exception message: An error occurred while communicating with the remote host. The error code is 0x800704CD. Thread information: Thread ID: 3 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status, Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments, IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32 finalStatus, Boolean& async) at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal) at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush) at System.Web.HttpResponse.Flush(Boolean finalFlush) at System.Web.HttpResponse.Flush() at System.Web.HttpResponse.End() at System.Web.HttpResponse.Redirect(String url, Boolean endResponse) at System.Web.HttpResponse.Redirect(String url) at CorrespondentPortalWebApp.Global.Session_Start(Object sender, EventArgs e) at System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) at System.Web.SessionState.SessionStateModule.CompleteAcquireState() at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
  • tmarq tmarq

    48 Posts

    Microsoft

    Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 08, 2010 02:41 PM|tmarq|LINK

    Amrendrakr,

    http://support.microsoft.com/kb/977453 fixes a bug that causes IHttpConnection::IsConnected to return incorrect values.  You should install it. 

    The error 0x800704CD corresponds to the message "An operation was attempted on a nonexistent network connection."  I'm still fairly certain the client disconnected.

    I also think you should follow my suggestion on how to use Redirect.  If you continue to have problems, please use the "Contact Microsoft Support" link at http://support.microsoft.com/.

    Thanks,
    Thomas

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jan 25, 2011 10:30 PM|arvestal|LINK

    anyone have a fix for my code a few posts above?  I have the patch, I'm not using a page, instead I'm using a handler. My code is very basic. where it just streams bytes of a memory stream to the browser.  I also have code to chunk the bytes by 1024 bytes at a time where it also produces this error.

    TIA, Allen

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jan 26, 2011 03:22 PM|HCamper|LINK

    Hello,

    Since you have a different issue,situation and system

    setup

    could you create a new post with

    information about the system.

    The code and errors and a description

    of what your doing.

    The current thread your tageed to has been answered and is easly mssed.

    for a specific problem and will get lost because of that.

    Thank You,

    Martin :)

    Windows and Linux work Together IT-Pros
    Community Member Award 2011
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jan 28, 2011 05:47 PM|arvestal|LINK

    OS: Windows Server 2008 64bit

    IIS 7

    Things I've tried, etc 

    1. I'm not using viewstate

    2. I'm not closing the browser and I'm waiting for the process to complete

    3. I have the patch installed.

    Below is my code, I only have 1 user and it blows up on the BinaryWrite.

    ErrorMessage: The remote host closed the connection. The error code is 0x80070057.

    ViewFileHandler.ashx::201010131034ARV RecipeId: 12  Stack::   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.HttpResponse.Flush()    at System.Web.HttpResponse.End()    at ViewFileHandler.ProcessRequest(HttpContext context) in d:\Web\projects\recipes\ViewFileHandler.ashx:line 133

    public void ProcessRequest (HttpContext context)
    {
        string id = context.Server.UrlDecode(context.Request.QueryString["recipeId"].ToString());
       
        MemoryStream ms = GetRecipeStream(id);
        byte[] recipe = ms.GetBuffer();
       
        try
        {
            context.Response.Clear();
            context.Response.Buffer = false;
            context.Response.ContentType = "Application/pdf";
            context.Response.BinaryWrite(recipe);
        }
        catch (System.Threading.ThreadAbortException)
        {
        }
        catch (System.Runtime.InteropServices.COMException)
        {
        }
        catch (Exception ex)
        {
            if (IsLoggerOn)
            {
                List<string> data = new List<string>();
                data.Add("ViewFileHandler.ashx::201010131034ARV");
                data.Add("RecipeId: " + id);

                Logger log = new Logger("ProcessRequest", data, ex);
                log.LogException();
            }
        }
    }

    public bool IsReusable
    {
        get {
            return false;
        }
    }

     

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jan 30, 2011 08:53 PM|HCamper|LINK

    Hello,

    Since you did not have a "Chance" to create a new post

    Please look at the information 

    at this link http://blog.whitesites.com/fixing-The-remote-host-closed-the-connection-The-error-code-is-0x80070057__633882307305519259_blog.htm  for ways to handle the coding error in C#.

    and look at

    this lnk here http://forums.asp.net/t/1486019.aspx for coding in ASP.NET. and

    a list of Faqs at the ASP.NET coding section here http://forums.asp.net/t/1360420.aspx 

    Post errors,issues & questions to this thread.

    Martin :)

    Windows and Linux work Together IT-Pros
    Community Member Award 2011
  • IIS7-Trouble-Shooting:Server-Failures-The I/O operation has been aborted because of either a thre...

    Feb 01, 2011 02:35 PM|HCamper|LINK

    Hello,

    For where the Web Site and code is located have you

    added accounts "IUSR","IIS_USERS" to have

    Read,Execute,List level permissions?

    The code and execution may lack the proper access rights.

    Post results answers &  questions to this thread.

    Martin :)

    windows

    Windows and Linux work Together IT-Pros
    Community Member Award 2011
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Apr 13, 2011 02:29 PM|Fp-India|LINK

     Hi ,

    I am getting same error 15 to 20 times in a day.

     I am using Window 2008 with IIS 7.0 and.SQL Server 2008.

    The below are the error :

     System.Web.HttpUnhandledException:
    Exception of type 'System.Web.HttpUnhandledException' was thrown. --->
    System.Web.HttpException: An error occurred while communicating with the remote
    host. The error code is 0x80070057.
    at System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.FlushCore(Byte[] status,
    Byte[] header, Int32 keepConnected, Int32 totalBodySize, Int32 numBodyFragments,
    IntPtr[] bodyFragments, Int32[] bodyFragmentLengths, Int32 doneWithSession, Int32
    finalStatus, Boolean& async)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushCachedResponse(Boolean isFinal)
    at System.Web.Hosting.ISAPIWorkerRequest.FlushResponse(Boolean finalFlush)
    at System.Web.HttpResponse.Flush(Boolean finalFlush)
    at System.Web.HttpResponse.Flush()
    at System.Web.UI.HttpResponseWrapper.System.Web.UI.IHttpResponse.Flush()
    at System.Web.UI.PageRequestManager.RenderFormCallback(HtmlTextWriter writer,
    Control containerControl)
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer,
    ICollection children)
    at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
    at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)
    at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)
    at System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output)
    at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer,
    ControlAdapter adapter)
    at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter
    adapter)
    at System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer)
    at
    System.Web.UI.HtmlFormWrapper.System.Web.UI.IHtmlForm.RenderControl(HtmlTextWriter
    writer)
    at System.Web.UI.PageRequestManager.RenderPageCallback(HtmlTextWriter writer,
    Control pageControl)
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer,
    ICollection children)
    at System.Web.UI.Control.RenderChildren(HtmlTextWriter writer)
    at System.Web.UI.Page.Render(HtmlTextWriter writer)
    at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer,
    ControlAdapter adapter)
    at System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter
    adapter)
    at System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
    Boolean includeStagesAfterAsyncPoint)
    --- End of inner exception stack trace ---
    at System.Web.UI.Page.HandleError(Exception e)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
    Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint,
    Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest()
    at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
    at System.Web.UI.Page.ProcessRequest(HttpContext context)
    at ASP.optin_aspx.ProcessRequest(HttpContext context)
    at
    System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
    completedSynchronously)

     Same application is running on Window 2003 with IIS 6.0 .But i am not getting this error from this configuration.

     

     

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Apr 14, 2011 05:50 AM|asidana|LINK

    I get this a lot, it looks like this is due to client disconnection before download frinished. although it is annoying, it does not cause any problem and safe to ignore. IIS shouldn't report it as error/warning though.
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Nov 17, 2011 03:56 PM|J.Samedov|LINK

    HCamper

    answers &  questions to this thread

    there can be another reason for the error: somebody killing sockets. In mine case it was antivirus programm: first connection - the exception, next closing and opening connections - no errors. After restarting client and server - the same story: at first time exception and then no exceptions. Unloading antivirus leads to disappearance of this kind exceptions
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Mar 06, 2012 01:05 PM|taschmidt|LINK

    We're still seeing these exceptions in production running Server 2008 x64 and intermittent periods of inactivity where our web app seems to freeze up but the dumps don't indicate that it's in our app. We have iiscore.dll version 7.5.7601.17514 installed. The hotfix says it's version 7.5.7600.20906. Can anyone tell me if that code fix is in our version? If not, how would I get it? Thanks, tim
  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Mar 09, 2012 04:19 PM|jimfr|LINK

    I still get this error often on many Windows 2008R2 machines all with latest Windows Updates applied.  Installing the KB977453 x64 hotfix always fails with a "this update is not applicable to your computer" message.  There's nothing in the hotfix article at http://support.microsoft.com/kb/977453 to say this fix has been incorporated into a service pack.

    How can I get the hot fix to install, or confirm it is in some service pack?

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    May 10, 2012 11:07 AM|ayavilevich|LINK

    We also have the same exception and when trying to install the hot-fix we get: "This update is not applicable to your computer".

    Can a Microsoft representative provide guideline or suggestions how to obtain a working version of the hot fix.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Jun 12, 2012 08:34 AM|atran1978|LINK

    We also  have those exceptions. Is there any news about it?

    iiscore.dll versions: 7.5.7601.17514, 7.5.7601.21686

    ---- Stack Trace ----

     

       System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(result As Int32, throwOnDisconnect As Boolean)

           (unknown file): N 2750572

       System.Web.Hosting.IIS7WorkerRequest.ReadEntityCoreSync(buffer As Byte[], offset As Int32, size As Int32)

           (unknown file): N 00049

       System.Web.Hosting.IIS7WorkerRequest.ReadEntityBody(buffer As Byte[], size As Int32)

           (unknown file): N 00023

       System.Web.HttpRequest.GetEntireRawContent()

           (unknown file): N 8791677

       System.Web.HttpRequest.FillInFormCollection()

           (unknown file): N 00105

       System.Web.HttpRequest.get_Form()

           (unknown file): N 00068

       System.Web.HttpRequest.get_HasForm()

           (unknown file): N 8743911

       System.Web.UI.Page.GetCollectionBasedOnMethod(dontReturnNull As Boolean)

           (unknown file): N 00097

       System.Web.UI.Page.DeterminePostBackMode()

           (unknown file): N 00063

       System.Web.UI.Page.ProcessRequestMain(includeStagesBeforeAsyncPoint As Boolean, includeStagesAfterAsyncPoint As Boolean)

           (unknown file): N 00133

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 30, 2012 11:07 PM|Hong Yang|LINK

    I have met the same issue when I migrated the website from Win 2003 to Win Server 2008 R2.

    Does someone have idea on it?

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 31, 2012 12:36 AM|necro_mancer|LINK

    hi hong,

    I highly advised you to start with a new thread so that everyone can see your post
    :)

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 31, 2012 02:26 AM|Hong Yang|LINK

    Hi necro_mancer

    Thanks.

     I have started a new thread:

    http://forums.iis.net/t/1192803.aspx

     Thanks & Best Regards

    Hong.

  • Re: The I/O operation has been aborted because of either a thread exit or an application request

    Oct 31, 2012 03:53 AM|runningfree|LINK

    http://www.uggbootscoupons.biz

    UGG Classic Tall Boots UGG Bailey Button Triplet Discount Ugg Boots coupons UGG Classic Mini Boots Find and share coupons UGG Fox Fur Boots www.uggbootscoupons.biz UGG Classic Short Boots Ugg Boots coupons UGG Bailey Button UGG Classic Cardy Boots