Hello Guys, I have 1 unique problem while accessing document library on share point site. i have 1 document library's custom view on share point site, this document library has several columns, custom view is grouped by Phase and then Stream column. when user expand phase it displays streams in side that phase and when user clicks on any of the stream it gives http 400 Bad request error. this problem is occurred with only 1 user, other users are able to access it without any problem. permission for this user is present at site level, document library level both. content of the document library inherits the permission from parent. any help will be appreciated.

The Web server (running the Web site) thinks that the data stream sent by the client (e.g. your Web browser) was 'malformed' i.e. did not respect the HTTP protocol completely. So the Web server was unable to understand the request and process i For me it looks like to be client issue not the SharePoint since other users are not facing the same issue. Folllow the link provided below that may be a help to you. http://www.checkupdown.com/status/E400.htmlBest Regards, Ashutosh | My Blog Site

Ashutosh, THanks For you reply. this problem comes only for that particular user only. if i login with my credentilas then there is no problem, so its not machine specific its something related to user's account. but i am not able to figure it out. also i have deleted all temporary files and cookies, but this also didnt worked out.

this problem may arise as well when you delete the AD user ID and recreate it in AD by the same userid. do you have the similar case as well.Best Regards, Ashutosh | My Blog Site

Hi Ashutosh, I dont think so but if that is the case then any idea what would be the solution for this?

I have got the Answer, This is Because User was a part of near about 152 AD groups. This issue may occur when the user is a member of many Active Directory user groups. When a user is a member of a large number of active directory groups the Kerberos authentication token for the user increases in size. The HTTP request that the user sends to the IIS server contains the Kerberos token in the WWW-Authenticate header, and the header size increases as the number of groups goes up. If the HTTP header or packet size increases past the limits configured in IIS, IIS may reject the request and send this error as the response. Please refer http://support.microsoft.com/kb/2020943