Home > Forums > IIS 7 > IIS 7 - Troubleshooting > The I/O operation has been aborted because of either a thread exit or an application request

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

Last post 12-04-2009 10:53 AM by brian-murphy-booth. 38 replies.

Average Rating Rate It (5)Thank you for the rating!

RSS

Page 1 of 3 (39 items) 1 2 3 Next >

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

06-10-2008, 3:46 AM

Jason Hill
Joined on 04-23-2006, 3:39 AM
Sydney, Australia
Posts 26

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

Reply Contact

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

06-10-2008, 6:07 AM In reply to

Rovastar
Joined on 03-13-2008, 10:00 AM
London, UK
Posts 1,797

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

Reply Contact

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

http://www.iisportal.com

06-10-2008, 6:48 AM In reply to

Jason Hill
Joined on 04-23-2006, 3:39 AM
Sydney, Australia
Posts 26

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

Reply Contact

Thanks for the response.

Some answers to your questions:

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.
The event viewer is showing the same exception that I have listed.
It is not a virtual machine.
We are connecting to a SQL Server 2005 database and I can't see anything in the logs that point to a problem there.

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)

06-10-2008, 5:12 PM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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

06-11-2008, 5:30 PM In reply to

Jason Hill
Joined on 04-23-2006, 3:39 AM
Sydney, Australia
Posts 26

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

Reply Contact

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

06-11-2008, 5:48 PM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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

07-22-2008, 12:03 AM In reply to

Jason Hill
Joined on 04-23-2006, 3:39 AM
Sydney, Australia
Posts 26

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

Reply Contact

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

Jason

08-13-2008, 12:39 PM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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.

12-15-2008, 10:35 AM In reply to

Alexey.UA
Joined on 12-12-2008, 2:05 PM
Posts 1

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

Reply Contact

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)

12-15-2008, 11:53 AM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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

04-29-2009, 7:25 PM In reply to

mbaocha
Joined on 04-21-2009, 8:38 PM
Posts 35

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

Reply Contact

Why not report such bugs to microsoft directly. They'll be in the best position to help you out. Anyway, I wish you the best ...

_____________________________________________________________________

Cheap Affordable Web Hosting & Design | Best PHP Linux Hosting | ASP.NET Windows Hosting

04-30-2009, 11:04 AM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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

06-24-2009, 3:51 PM In reply to

vishalpatole
Joined on 06-24-2009, 7:40 PM
Posts 1

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

Reply Contact

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

07-14-2009, 2:13 PM In reply to

tmarq
Joined on 06-11-2002, 2:44 PM
42
Posts 43

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

Reply Contact

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

07-15-2009, 11:29 AM In reply to

jpbaker22
Joined on 05-28-2009, 2:51 PM
Posts 2

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

Reply Contact

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.

Page 1 of 3 (39 items) 1 2 3 Next >