Symptoms

When Users open reports and then viewflow and receive the 400 bad request IE become un responsive.

 

Diagnoses

• When refreshing the cache the error goes away.
• Then when you navigate from management console to Reports andgt Process Overview andgt view the Data or Folio view and then go make to Process Overview or Management console a 404 message appears.
• IE then gets unresponsive.
This is due to header size / cookie size, MaxTokenSize and Kerberos Token Bloat
• The MaxTokenSize by default is 12,000 bytes. This has been the default value since Windows 2000 SP2 and still remains in Windows 7 and Windows 2008 R2. As companies grow so do the groups within your organization. If your Kerberos token becomes too big your users will receive error messages during login and applications that use Kerberos authentication will potentially fail as well.
• When opening viewflow K2 request the claim via STS and this can contribute to the header/cookie size

 

Resolution


Change the default value of the MaxTokenSize registry entry is 48000 bytes by:
1. Start Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:
SystemCurrentControlSetControlLsaKerberosParameters
3. If this key is not present, create the key. (even if you are not using Kerberos)

To do so:
a. Click the following key in the registry:
SystemCurrentControlSetControlLsaKerberos
b. On the Edit menu, click Add Key.
c. Create a Parameters key.
d. Click the new Parameters key.

4. On the Edit menu, click Add Value, and then add the following registry value:
Value name: MaxTokenSize
Data type: REG_DWORD
Radix: Decimal
Value data: 48000
5. Quit Registry Editor.
6. Clear the browser cache (uncheck Preserve Favourite)

http://www.iis.net/learn/troubleshoot/diagnosing-http-errors/troubleshooting-http-400-errors-in-iis