asked on

HTTP 400 Bad Request, Timer_EntityBody DefaultAppPool

Hi experts,

we have a problem with an ASP.NET 2.0 application running on a Windows 2003 Server (SP1) os with IIS6.0.

When using the page from the local network everything works fine. The same with most of our customer networks.
However when using the page from certain customer networks we receive an HTTP 400 Bad Request error. This occurs on just a few pages when clicking on asp buttons causing a postback.

The IIS logfiles look like this:

2006-07-24 08:54:00 W3SVC221004838 192.168.8.10 POST /kvp/Suggestion.aspx - 80 - 62.2.135.98 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 400 0 64

The HTTPERR logfile shows the following entries:

2006-07-24 08:54:20 62.2.135.98 14442 192.168.8.10 80 HTTP/1.1 POST /kvp/Suggestion.aspx - 221004838 Timer_EntityBody DefaultAppPool

Any help is appreciated! Thank you!

RedKelvin

The microsoft description for a timer_entitybody error is

The connection expired before the request entity body arrived. When it is clear that a request has an entity body, the HTTP API turns on the Timer_EntityBody timer. Initially, the limit of this timer is set to the ConnectionTimeout value (typically 2 minutes). Each time another data indication is received on this request, the HTTP API resets the timer to give the connection two more minutes (or whatever is specified in ConnectionTimeout).

An entry in the httperr log showing Timer_EntityBody indicates IIS did not receive any data from a client request and the request timed out (as determined by the connection timeout metabase property). Client requests with large content length headers can cause this error.

see if these are any help
http://support.microsoft.com/kb/886461/
http://support.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.inetserver.iis&tid=7ae29089-fa57-4ce1-8737-fd2c070b1558&p=1

Hope that is some help
RedK

ibitech

ASKER

The source for the problem was an wrong entry in the MTU-Value for the network.
We adjust the value with a program called "dr. tcp" and everything works perfectly

Thanks RedK for your suggestions

ASKER CERTIFIED SOLUTION

ee_ai_construct

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

codejunky

we recently had a similar problem, and I will say that this one is very tough to diagnose. The problem was created by our ISP adding a new switch and lowering the MTU to 1500. This should be acceptable and was for all regular internet traffic. It only failed on websites that where SSL encrypted. To correct the problem we changed the MTU on the router interface to 1450(I believe) and everything started working properly.