Intermittent 400 Bad Request - Invalid Verb SharePont 2010

Hey,

This is a long shot that someone has seen this or maybe can give some hints on finding the problem.

We are getting a rare (once per day) 400 Bad Request - Invalid Verb error in SharePoint 2010 during a POST - this has happened when adding a ListItem.  Once the page is refreshed it works perfectly.

We have an on-premise instance of SharePoint 2010, it happens on all browsers.

The request header looks exactly the same for a succesful update as athe error. Any ideas where to start?

The response in Fiddler is

HTTP/1.1 400 Bad Request

Content-Type: text/html; charset=us-ascii

Server: Microsoft-HTTPAPI/2.0

Date: Thu, 06 Mar 2014 10:12:48 GMT

Connection: close

Content-Length: 326

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">

<HTML><HEAD><TITLE>Bad Request</TITLE>

<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>

<BODY><h2>Bad Request - Invalid Verb</h2>

<hr><p>HTTP Error 400. The request verb is invalid.</p>

</BODY></HTML>

From the post

POST http://...PAGENAME.aspx HTTP/1.1

Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*

Accept-Language: en-GB

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; GTB7.5; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; InfoPath.3)

Content-Type: multipart/form-data; boundary=---------------------------7de27631102b2

Accept-Encoding: gzip, deflate

Content-Length: 0

Host: XXX

Cookie: OfflineClientInstalled=1; s_cc=true; s_sq=wileyportal%3D%2526pid%253DFunctions%25257CTechnology%25257CPages%252520-%252520WGT%2526pidt%253D1%2526oid%253Dfunctiononclick()%25257BWzClick(event%25252C'g_07E87395550E47F7A3537187A352BC28')%25257D%2526oidt%253D2%2526ot%253DTABLE%2526oi%253D1939; s_vnum=1395390204033%26vn%3D24; s_invisit=true; s_visit=1; WSS_KeepSessionAuthenticated={618701bc-c2b7-48e3-b7ff-a55e68ea6c5f}; ASP.NET_SessionId=4c0kd245pgy3kj55zxztti45; Ribbon.WikiPageTab=1259870|-1|444|-1204987594; previousLoggedInAs=; loginAsDifferentAttemptCount=; http://url 09:29:20; Ribbon.Document=1276887|0|31|-564700907; Ribbon.Library=1276887|3|61|-564700907; Ribbon.Permission=1259887|-1|627|-233240519; Ribbon.List=1276887|4|58|-564700907; Ribbon.ListForm.Edit=682557|-1|364|-965405633; Ribbon.ListItem=1276887|-1|549|-564700907; Ribbon.EditingTools.CPEditTab=1259870|-1|454|-1204987594; Ribbon.EditingTools.CPInsert=1259870|-1|783|-1204987594; Ribbon.Image.Image=1259870|-1|382|-1204987594

Connection: Keep-Alive

Pragma: no-cache

Authorization: NTLM TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAGAbEdAAAADw==

Referer: http://...page.aspx

March 6th, 2014 6:10am

Hi,

For narrowing down the issue, we need more investigations. Please provide more information about:

  1. What web form were you posting? Is it an customized web form page? Or you could save more detail information in Fiddler and send to me via v-retu@microsoft.com .
  2. Since it is an intermittent issue, is there any application-layer awareness intermediate device such as proxy or reverse proxy/gateway between your client machine and SharePoint server? If so, please exclude the IP of SharePoint Server in the Proxy and test the issue again.
  3. Please check your IIS log and see if there is any error message related error 400.
  4. Moreover, please check the performance of your SPS server, WFE and especially SQL server.

Regards,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

Free Windows Admin Tool Kit Click here and download it now
March 10th, 2014 5:23am

Hi Rebecca, thanks for your reply.

1.  Creating / Editing a Listitem using the OOTB form.  No customisation at all.

2.  Good call - there is a h/w network load balancer.  I will change my host file settings to connect directly to a WFE and monitor for a few days.

3.  The IIS log was not very informative - just gave the IP address and 400 - Bad Verb.  I will post when it happens again.

4.  The performance of all the servers is fine but the I will check when there is a repeat of the issue.#

Cheers

March 10th, 2014 6:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics