I found the answer here: http://www.microsoftadmin.net/artykul35.html
in-place eDiscovery & hold - Error 400 Bad Request
Hi guys, I'm having a problem on Exchange Server 2013 CU23.
When clicking on eDiscovery & hold I am getting error "The request failed. The remote server returned an error: (400) Bad Request." and I don't know where else to "fix" this problem.
I have already performed:
- Windows Update
- I applied the patch Exchange2013-KB5001779-x64-en
- Disabled\Enable TLS 1.0 and 1.1
- I prepared again the Schema and AD
And yet the problem persists.
It is only in this option eDiscovery & hold, in the others you are accessing.
Has anyone caught this error?
5 answers
Sort by: Newest
-
-
Rafael Komatsu 6 Reputation points
2021-09-29T16:44:33.147+00:00 Hello gentlemen, good afternoon.
Microsoft found the problem and it was the HTTP, EWS (Exchange BackEnd), attribute "msExchInternalNLBBypassHostName" that was missing port 444 forwarding.
It should look like this: https://fqdn_server:444/ews/exchange.asmx
In EWS (Default) this attribute is Null.
It worked for me guys.
-
Benjamin Huang 1 Reputation point
2021-09-28T00:43:44.707+00:00 I too am facing the same issue. Would it have anything to do with exchange hybrid?
-
Rafael Komatsu 6 Reputation points
2021-09-14T19:10:15.427+00:00 Hi joyceshen-msft, I did it as requested, but it still has an error message.
I left only TLS 1.2.
I revalidated my user's permission and I'm in the Compliance Management group.
To get an idea, I climbed a new server and applied this configuration and the latest updates of Windows Server 2012 R2 and Exchange Server 2013 CU23 and nothing.
I don't know what it can be anymore.
-
Joyce Shen - MSFT 16,646 Reputation points
2021-09-13T02:06:09.997+00:00 This thread discussed the same issue as yours, please check the solution below: Exchange 2013 e-Discovery not working after disabling TLS 1.0 and 1.1
Add the following registry keys to make WinHTTP and .NET Framework use TLS 1.2
ENABLING TLS 1.2 ON EXCHANGE SERVER 2013 & 2016WinHTTP:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp “DefaultSecureProtocols”:dword:00000a80 2. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp “DefaultSecureProtocols”:dword:00000a80
.NET Framework:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 “SystemDefaultTlsVersions”=dword:00000001 2. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 “SystemDefaultTlsVersions”=dword:00000001
I used IISCrypto to disable TLS 1.0/1.1 and enable TLS 1.2 on my Exchange server, after that, when I performed an eDiscovery search by EAC or the command "New-MailboxSearch" in EMS, I got a similar error. Finally, I tried to enable TLS 1.2 for WinHTTP and .NET Framework, after rebooting my server, eDiscovery can work without any error in EAC and EMS.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.