HttpException "Request timed out" - how to handle?

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Hi...

We've got some company web forms that can transfer a reasonable amount of
data (~200k, half in view state and half in a big text blob). The company
server is running IIS 6/.Net v2.0.50727.

The thing that's perplexing is that we have 3 people in the office who
consistently get HttpException "Request timed out" errors on the form when
everyone else processes it fine (and quickly).

I've seen a number of posts online about how tricky this kind of thing is to
diagnose, since this exception can't be trapped and won't give you a stack
trace of what was executing at the time. Most usually coming to the
conclusion that the POST got split into multiple packets and that for these 3
users 1 or more of the packets are going astray.

The question would be why just those 3 users? We're all sitting inside the
same office network, going to the same company server, using the same browser
(IE 8).

Those same users say that when they take their laptops home and run it from
there, it works fine. That lends more support to some kind of networking
issue.

In the office when it works for someone, it takes just a few seconds (not
the full ScriptTimeout). This also seems to point to network issues but why
for just a few people consistently?

Are there any network settings I should be checking? Even if I get a packet
sniffer and show the last half of the POST is never acked, it still doesn't
say what to do about it...

Any pointers would be appreciated...

Thanks
Mark
 
Since this is isolated to 3 machines (not users), first I would check the
security settings for those machines. Try setting security levels to the
minimum and try the POST.

-Scott
 
Hi,

Can you try to set a longer timeout for the httpruntime to check if it is a
really timeout issue?
<httpRuntime executionTimeout="1000" maxRequestLength="2000000" />

And you can use IIS6 to race the web page
http://technet.microsoft.com/en-us/library/cc728367(WS.10).aspx


--
Sincerely,

Vince Xu

Microsoft Online Support


==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

MSDN Managed Newsgroup support offering is for non-urgent issues where an
initial response from the community or a Microsoft Support Engineer within
2 business day is acceptable. Please note that each follow up response may
take approximately 2 business days as the support professional working with
you may need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations that require urgent,
real-time or phone-based interactions. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================

--------------------
| Thread-Topic: HttpException "Request timed out" - how to handle?
| thread-index: AcqhNJYmmPdOknbISQ+0aIbLHPA5rg==
| X-WBNR-Posting-Host: 72.46.169.226
| From: Mark <[email protected]>
| Subject: HttpException "Request timed out" - how to handle?
| Date: Fri, 29 Jan 2010 14:44:16 -0800
| Lines: 36
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.dotnet.framework.aspnet:96110
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Hi...
|
| We've got some company web forms that can transfer a reasonable amount of
| data (~200k, half in view state and half in a big text blob). The
company
| server is running IIS 6/.Net v2.0.50727.
|
| The thing that's perplexing is that we have 3 people in the office who
| consistently get HttpException "Request timed out" errors on the form
when
| everyone else processes it fine (and quickly).
|
| I've seen a number of posts online about how tricky this kind of thing is
to
| diagnose, since this exception can't be trapped and won't give you a
stack
| trace of what was executing at the time. Most usually coming to the
| conclusion that the POST got split into multiple packets and that for
these 3
| users 1 or more of the packets are going astray.
|
| The question would be why just those 3 users? We're all sitting inside
the
| same office network, going to the same company server, using the same
browser
| (IE 8).
|
| Those same users say that when they take their laptops home and run it
from
| there, it works fine. That lends more support to some kind of networking
| issue.
|
| In the office when it works for someone, it takes just a few seconds (not
| the full ScriptTimeout). This also seems to point to network issues but
why
| for just a few people consistently?
|
| Are there any network settings I should be checking? Even if I get a
packet
| sniffer and show the last half of the POST is never acked, it still
doesn't
| say what to do about it...
|
| Any pointers would be appreciated...
|
| Thanks
| Mark
|
 
Hello,

Since I haven't seen your reply after I last posted my reply. Did you
resolve this?

--
Sincerely,

Vince Xu

Microsoft Online Support

--------------------
| Thread-Topic: HttpException "Request timed out" - how to handle?
| thread-index: AcqhNJYmmPdOknbISQ+0aIbLHPA5rg==
| X-WBNR-Posting-Host: 72.46.169.226
| From: Mark <[email protected]>
| Subject: HttpException "Request timed out" - how to handle?
| Date: Fri, 29 Jan 2010 14:44:16 -0800
| Lines: 36
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4325
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.dotnet.framework.aspnet:96110
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Hi...
|
| We've got some company web forms that can transfer a reasonable amount of
| data (~200k, half in view state and half in a big text blob). The
company
| server is running IIS 6/.Net v2.0.50727.
|
| The thing that's perplexing is that we have 3 people in the office who
| consistently get HttpException "Request timed out" errors on the form
when
| everyone else processes it fine (and quickly).
|
| I've seen a number of posts online about how tricky this kind of thing is
to
| diagnose, since this exception can't be trapped and won't give you a
stack
| trace of what was executing at the time. Most usually coming to the
| conclusion that the POST got split into multiple packets and that for
these 3
| users 1 or more of the packets are going astray.
|
| The question would be why just those 3 users? We're all sitting inside
the
| same office network, going to the same company server, using the same
browser
| (IE 8).
|
| Those same users say that when they take their laptops home and run it
from
| there, it works fine. That lends more support to some kind of networking
| issue.
|
| In the office when it works for someone, it takes just a few seconds (not
| the full ScriptTimeout). This also seems to point to network issues but
why
| for just a few people consistently?
|
| Are there any network settings I should be checking? Even if I get a
packet
| sniffer and show the last half of the POST is never acked, it still
doesn't
| say what to do about it...
|
| Any pointers would be appreciated...
|
| Thanks
| Mark
|
 
Back
Top