IIS 7 - Troubleshooting

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

brian-murphy-booth — Fri, 04 Dec 2009 15:53:05 GMT

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

MattDuguid — Tue, 01 Dec 2009 00:15:51 GMT

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:

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

tmarq — Mon, 30 Nov 2009 17:37:38 GMT

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

whitesites — Fri, 27 Nov 2009 15:17:00 GMT

Post some source code.

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

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

jonesri — Fri, 27 Nov 2009 11:44:31 GMT

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

gunjan.gandhi — Thu, 22 Oct 2009 09:31:28 GMT

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

whitesites — Thu, 22 Oct 2009 07:26:42 GMT

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

gunjan.gandhi — Thu, 22 Oct 2009 07:16:06 GMT

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">

<body>

<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

whitesites — Thu, 22 Oct 2009 06:58:59 GMT

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

gunjan.gandhi — Thu, 22 Oct 2009 06:51:08 GMT

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

whitesites — Thu, 22 Oct 2009 05:51:57 GMT

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

gunjan.gandhi — Thu, 22 Oct 2009 05:38:16 GMT

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

MattDuguid — Thu, 17 Sep 2009 04:35:53 GMT

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

whitesites — Sun, 13 Sep 2009 00:50:39 GMT

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

jb — Thu, 27 Aug 2009 20:21:07 GMT

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.