IIS 5 & IIS 6
IIS Request Timed out error
Last post Jan 20, 2010 04:33 PM by aRs3N1c42
Sep 02, 2009 12:24 AM|vcontin|LINK
I have a web application in IIS6 windows 2003 R2.
Connection Timeout is 3,600 seconds.
Enable Session State is set. Session timeout is 60 minutes.
ASPscript timout is 90 minutes
The Application Pool is not set to recycle the process. Maximum Used memory is above the usage I am seeing. It's not set to shut down the worker processes after iddle time.
Yet the session times out after 10 minutes regularly. The Timeout in the Web.config is set for 60 minutes. I am not sure what I may be missing.
Any help would be greatly appreciated.
Thanks in advance,
I get the following error in the Application Event log
Event ID: 1309
Source: ASP.NET 2.0.50727.0
Process ID: 5788
Process name: w3wp.exe
Account name: YYZ\Pool_yyz
Exception type: HttpException
Exception message: Request timed out.
Request URL: https://yyz.1234domain.com:443/DownloadRecords.aspx
Request path: /DownloadRecords.aspx
User host address: xxx.xxx.xxx.xxx
Is authenticated: False
Thread account name: Domain\user
Thread ID: 9
Thread account name: Domain\User
Is impersonating: False
Custom event details:
For more information, see Help and Support Center at
Sep 02, 2009 09:29 PM|davcox|LINK
Have you checked the http log? What does the IIS log say?
You may be running into the Timer_MinBytesPerSecond if the response is going really slow in terms of bytes per second ...
Sep 02, 2009 09:54 PM|vcontin|LINK
Thank you for your reply. Here's what the HTTPEERR log says (slightly modified)
2009-09-02 16:56:13 126.96.36.199 59940 188.8.131.52 80 HTTP/1.1 POST /DownloadRecs.aspx - 663665144 Connection_Dropped MyAppPool
I don't see a specific message. The normal log looks like the following entry.
2009-09-02 17:39:40 W3SVC663665144 184.108.40.206 POST /DownloadRecords.aspx 80 - 220.127.116.11 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+InfoPath.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0
Thanks again for your assistance.
Sep 02, 2009 10:58 PM|davcox|LINK
So this looks like the client is dropping the connection rather than the server ... does this happen on all clients or just some subset?
Sep 02, 2009 11:10 PM|vcontin|LINK
Thanks again Dave,
This is a system that I am inheriting. It generates an Excel file and this process takes in some instances over half an hour. On this instances we get the error at exactly ten minutes once the process starts.
It's a horrible process but I'm stuck with it at the moment. The strange thing is that if I run it on machine, in Visual Studio (2008) it works fine. The browser waits the required time and the process completes. But if I run this agains IIS, the process
is stopped 10 minutes into the process.
I am not a Web person, I typically work on back-end systems but I am working with this system now. Once again, I appreciate your willingness and your assistance.
Oct 20, 2009 10:28 PM|LostWithIIS|LINK
i am experiencing the exact same problem. That a long running request times out after 10 minutes yet my configurations at set to time out after one hour. In addition, my IIS also have the Connection_Dropped message.
did you ever come up with a fix for this?
Oct 21, 2009 04:42 PM|tomkmvp|LINK
In both of your situations it could be the web browser that is terminating the connection. Browsers will not wait forever to receive a response.
It sounds like if your application is taking this long to generate a complete response then perhaps the web platform is not the correct choice for your application and you need to look into another method to generate the results.
Oct 21, 2009 04:51 PM|LostWithIIS|LINK
Thanks for the response. Let me clarify my situation:
I have reporting web server where some reports may take over 10 minutes to generate. If I open up a browser down at our datacenter, the report comes back fine. However, if I run the same report (and in the same browser) remotely it seems to crap out after
10 minutes and I see the connection_dropped after 10 minutes.
Is there any way to capture the event to see what is specifically terminating the connection? I have checked with my network guys and they say there is nothing on the firewall end of things that would be killing these long connections.
Jan 20, 2010 04:33 PM|aRs3N1c42|LINK
I have only scratched the surface of what Fiddler can do, but I understand it is useful in diagnosing issues such as this.