Fix Up “HTTP 400 Bad Request” error in Exchange Server?
Updated On - January 16, 2023 by Henry Bray |Reading Time: 4 minutes
It’s a web-based edition of the Microsoft Outlook desktop application, previously called Outlook Web App. In the event that you’re at a remote area, Outlook on the web could allow you to gain access to the contents of your Exchange account. Inboxes and all folders it contains will be accessible. If, upon connecting to the servers, it’s incapable of locating your website’s URL, it displays the error code 400. This HTTP 400 Bad Request error in Exchange Server signals the server is not able to fulfill your request.
Internet Explorer is able to connect to the server, but the website is not able to found due to an issue with the address, leading to an HTTP 400 Bad Request error.
Exchange Server 2013 Client Access Server or Microsoft Exchange 2016 (running client access service) might display an error message similar to the one above when the user attempts to redirect the HTTP requests to an earlier version Exchange server.
Most of the time, this issue is encounter with Exchange Server 2016 (Enterprise and Standard Edition), Exchange 2013 (Enterprise Standard Edition as well as Enterprise Edition) and Exchange 2010 (Standard and Enterprise Edition).
Related Blog: Extract Exchange Mailbox Data from EDB File to PST
The following information could be found in the Exchange 2013. Client Access records.(\Logging\HttpProxy\):
2014-07-24T16:56:17.806Z,ddf5379e-4a97-4833-b331-36328b9f8b58,15,0,913,7,,Owa,outlook.Wingtiptoys.com,/owa/,,Negotiate,True,WINGTIPTOYS \user003,,Sid~S-1-5-21-3205615561-4199783494-2467053687-1128,Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729),192.168.137.113,WINGTIP-E2K13,400,400,,GET,Proxy,wingtip-e2k10.wingtiptoys.com,14.03.0123.000,IntraForest,WindowsIdentity-ServerCookie,Server~WINGTIP-E2K10.Wingtiptoys.com~1937997947~07/24/2014 17:01:18,,,0,342,1,,4,14,,0,,0,,0,0,,0,46.8744,0,,,,18,0,1,0,0,1,38,1,20,20,20,24,43,,,BeginRequest= 2014-07-24T16:56:17.759Z;CorrelationID=;ProxyState-Run=None;ProxyToDownLevel=True;BeginGetResponse=2014-07-24T16:56:17.791Z;OnResponseReady=2014-07-24T16:56:17.806Z;EndGetResponse=2014-07-24T16:56:17.806Z;ProxyState-Complete=ProxyResponseData;EndRequest=2014-07-24T16:56:17.806Z;,WebExceptionStatus=ProtocolError;ResponseStatusCode=400;WebException =System.Net.WebException: The remote server returned an error: (400) Bad Request. atSystem.Net.HttpWebRequest.EndGetResponse(IAsyncResultasyncResult) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2a.b__28();
Additionally to that, the HTTPErr logs of those servers Exchange Server 2010 and Exchange Server 2007 Client Access servers could contain the error message below:
2014-07-24 16:48:06 192.168.137.113 53335 192.168.137.110 443 HTTP/1.1 GET /owa/ 400 – RequestLength –
The root of HTTP 400 error could be described as follows:
The problem occur when user account’s participation in multiple Active Directory groups. This error has been experienced when the proxy request is made by the Exchange 2019, 2013 servers to 2010 server’s Client access server.
Fix the issue in HTTP 400 Bad Request
To resolve the problem, the user’s account should be removed from various Active Directory groups. In addition, all Exchange Server 2010 CAS instances should have their MaxFieldLength and MaxRequestBytessubkeys set to their maximum values.
Utilizing the first approach that we’ll explore how you can make a change in the subkey parameter within Exchange Server 2010.
Go to each Exchange Server 2010 Client Access Server one at a time and look for the following subkey.HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Review for the MaxFieldLength and MaxRequestBytes entry of their respective tables, and make the changes as follows:
|Value Name||Type||Value Data||# Value Base|
Begin with a restart of your Client Access Server and then retrying to perform the proxy procedure.
Important: Enter these numbers manually if you’re unable to find the entries for MaxFieldLength as well as the MaxRequestBytes.
Increase the value for these variables and you’ll be able transmit more HTTP packets through IIS, while growing capacity of the RAM the Http.sys makes use of. Spyware and viruses that are risky are possible due to it. The second method is described below.
The other option is to delete the account of the user from all the Active Directory roles groups. It’s possible for an account in Active Directory to be a part of multiple groups at the same time. It is likely this proxy’s account is the cause of problems with the Bad Request issue since it’s an active member of multiple groups at one time.
You can remove the user account from a group using an Exchange Shell cmdlets. Here’s an example to you understand.
What you need to do is: Jonathan’s group members may be removed by using the command: remove-ADGroupMember.
As a result of this decision Jonathan’s account will be delete in his account in the Networking Role Group. Utilizing one of the above-mention alternatives, Exchange Server 2010, 2013, 2016, and 2019 could be configur to perform proxy services. Alongside this issue and it is possible that the Exchange environment is susceptible to server downtimes. To ensure your safety and security, you must use an expert tool to deal with EDB corrupted files or Exchange Server malfunctions. It is possible to use The Regain Exchange EDB Recovery to fix all Exchange database damaged or lost data with this tool.
Utilizing Regain Exchange EDB Recovery Tool
Exchange EDB Recovery is hailed as the best solution for damaged Exchange Server. If you notice any signs of degrading or degradation, it can be access to review your off-line Exchange databases. The tool allow users to access mailbox that was deleted by Exchange server. An overview of recover data as well as the capability to save recover data in various formats will be made available to you.
Free Download100% Secure Buy NowPrice: $99
If you make an HTTP request is submit to an older version of Exchange Server through the Exchange 2013/2016/2019 Client Access Server, it is possible to get an HTTP 400 Bad Request error. To fix this issue in Exchange 2010, you’ll need to remove the user account from certain AD groups or update the MaxFieldLength and MaxRequestBytessubkey settings.
- Your Mailbox has been Temporarily Moved on Exchange Server
- Perform Exchange Server recovery due to Event ID 489!
- How to resolve Jet Engine Errors in MS Exchange Server?
- Resolve Most Common Exchange Server Database mounting issues?
- How to Delete Exchange Log Files
- Solve “Mailbox export stalled due to source disk latency”
- How to Resolve Stuck Offline Mode Issue in Outlook?
6 thoughts on “Fix Up “HTTP 400 Bad Request” error in Exchange Server?”
Thanks for ones marvelous posting! I truly enjoyed reading it, you will be a great author.I will be sure to bookmark your blog and will eventually come back sometime soon.
I want to encourage continue your great job, have a nice weekend!
I have been browsing online more than 2 hours today, yet I never found any interesting article like yours.
It’s pretty worth enough for me. Personally, if all webmasters and bloggers made good content as you did, the internet will be much more useful than ever before.
Your style is so unique in comparison to other people I’ve read stuff from. I appreciate you for posting when you’ve got the opportunity, Guess I’ll just bookmark this web site.
I’ve been browsing online more than three hours as of late, but I by no means discovered any attention-grabbing article like yours. It’s pretty worth enough for me. In my view, if all website owners and bloggers made good content as you probably did, the internet will probably be much more helpful than ever before.
Somebody essentially help to make significantly posts I would state.
This is the first time I frequented your website page and so far?
I amazed with the research you made to make this actual post incredible.
I found this article really helpful as I was recently having this issue! It was easy to follow, and the steps were clearly explained. I was able to fix the problem with the help of this article. Thanks to the author a lot!