"This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address."

When the user proxies an HTTP request from an Exchange Server 2013 Client Access Server) or Microsoft Exchange Server 2016 (running client access service) or to an older version of Exchange server, then you may get a bad request error like the above.

Mostly this issue is found in Exchange Server 2016 (Enterprise & Standard Edition), Exchange Server 2013 (Enterprise & Standard Edition), and Exchange Server 2010 (Standard & Enterprise) environments.

Also, Exchange Server 2013 Client Access server show the following in the Exchange logs ( <Exchange Server Install Path>\Logging\HttpProxy\<Http resource>):

Moreover, the Exchange Server 2010 and Exchange Server 2007’s Client Access Server may have the following error message in their HTTPERR logs:

Cause of the HTTP 400 Bad Request Error

The cause of the error is the presence of your account in the multiple Active Directory Groups. The error may occur in the proxy request form the Client Access Server of Exchange Server 2016 or 2013 to that of Exchange Server 2010.

Resolve the HTTP 400 Bad Request Issue

To resolve the issue, you need to remove the user account from multiple Active Directory Groups. Also, increase the MaxFieldLength and MaxRequestBytes subkeys for all Exchange Server 2010 CAS.

Method 1

First, we will learn to change the subkey parameter in the Exchange Server 2010.

1. Go to each Exchange Server 2010 Client Access Server and try to locate the following subkey;
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
2. Check the MaxFieldLength and MaxRequestBytes entries and change the value in their tables:
   

   Value Name	Value Type	Value Data	Value Base
   MaxFieldLength	DWORD	65536	Decimal
   MaxRequestBytes	DWORD	65536	Decimal

3. Restart the Client Access Server and try to run the proxy process again.

NOTE:

• If you do not find the entries for the MaxFieldLength or MaxRequestBytes, then create these entries manually.
• Increasing the values of these entries will allow larger HTTP packets to be sent to IIS and will cause the Http.sys to use more memory. It may further increase the chances of malicious malware and spyware attacks.

Method 2

The second method is removing the user account from the different role groups of the Active Directory. A a user account can be a member of multiple groups. The Bad Request error occurs when a user account that is running the proxy service is a member of multiple groups.

You can remove the user account from the group using the Exchange Shell cmdlets. Here is the example –

Example –

The command will remove the account name Jonathan from the Networking Role Group.

The above two methods are a workaround that may allow you to run the proxy services from Exchange Server 2013 and 2016. However, apart from this error, Exchange environment is vulnerable to corruption issues and server crashes. If you do not want to face any grave situation, then you should have a professional tool to handle a corruption of EDB files or Exchange Server crashes. Kernel for Exchange Server is one such software that will allow you to fix any Exchange database corruption and recover any lost data.

Kernel for Exchange Server

Kernel for Exchange Server is a top-rated Exchange Recovery software for the Exchange Server corruption issues. It can access the offline Exchange database files and scan them for any possible corruption. It will retrieve both corrupt and deleted items back. It will show you a clean preview of the recovered data and allow you to save the recovered items in the multiple output formats suitable to you.