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

View Complete Thread
  • tmarq tmarq

    48 Posts


    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


    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.