In setting up the exchange 2013 environment here for ediscovery and hold options, I had made sure I was in the compliance management membership role and also assigned the addtional roles of Data Loss Prevention and Information Rights management and Retention Management as well. I had inherited this Exchange 2013 env from a former employee so I wonder if something is not set up properly in IIS perhaps.
When I try to run a test search in eDiscovery I get a status failed and when I look at the details, I get this below which seems to me like some sort of IIS persmissions issue or such. I cannot find any info on the web that pinpoints this error but seem to see other web issues with the some type of issue which is The request failed with a HTTP Status 405. I redacted the server info to keep private of course, but here is the exact errors I am seeing. Wondering if anyone has any ideas on this and maybe has seen this themselves in their eDiscovery setup. Thanks for any info or pointers!
Export failed with error type: 'FailedToSearchMailboxes'. Details: The request failed with HTTP status 405: Method Not Allowed. Endpoint: https://prod-exch-01d.administration.sec.state.vt.us:444/owa HttpContext: X-AnchorMailbox:brian.howard@sec.state.vt.us client-request-id:345104ae-e66d-42e7-95ed-1a316d58164d Allow: GET, HEAD, OPTIONS, TRACE X-Content-Type-Options: nosniff X-OWA-Error: Microsoft.Exchange.Clients.Owa2.Server.Core.OwaADUserNotFoundException X-BackEnd-Begin: 2018-06-14T16:54:09.904 X-BackEnd-End: 2018-06-14T16:54:09.904 Persistent-Auth: true X-DiagInfo:PROD-EXCH-01D X-BEServer: PROD-EXCH-01D X-UA-Compatible: IE=EmulateIE7 Content-Length: 1293 Content-Type: text/html Date: Thu, 14 Jun 2018 20:54:08 GMT Set-Cookie: ClientId=FDENWBKEIBTTPCDNWG; expires=Fri, 14-Jun-2019 20:54:09 GMT; path=/; HttpOnly Server: Microsoft-IIS/8.5 WWW-Authenticate: Negotiate oRswGaADCgEAoxIEEAEAAACJ3sgDWJE5cQAAAAA= X-Powered-By: ASP.NET ScenarioData: Exchange\15.00.1210.000\EDiscovery\EWS\QL=85&BI=636646064498572573&RT=636646064498572573&SID=