in-place eDiscovery & Hold - 404 Not Found

Hi

In our Exchange system we are having an issue where we keep getting a 404 error when trying to manage in-place eDiscovery & Hold we receive a 404 error.

This occurs both via the EAC and when running the relevant command like Get-MailboxSearch

[PS] C:\Windows\system32>Get-MailboxSearch
The request failed. The remote server returned an error: (404) Not Found.
    + CategoryInfo          : NotSpecified: (:) [Get-MailboxSearch], DataSourceOperationException
    + FullyQualifiedErrorId : [Server=EXMBX01,RequestId=2eefcb57-8a3b-4ad9-83a9-57b5ff889e69,TimeStamp=07/08/2015 14
   :19:47] [FailureCategory=Cmdlet-DataSourceOperationException] C792466D,Microsoft.Exchange.Management.Tasks.GetMail
  boxSearch
    + PSComputerName        : exhtcas01.services.local

Our mailbox servers are separate to the CAS servers. I have a dev enviroment where this issue is not occuring which is making this more difficult. Both are running Exchange 2013 CU9. The only difference is the DEV server is a single multi roled server.


I have checked Authentication settings on the EWS directory and they look fine.

Any idea's ?

Any help is appreciated

Thanks

August 7th, 2015 10:25am

You get the error in both dev and production?  Have you tried running it with the -Verbose parameter?  Have you verified that your account has the required rights?

https://technet.microsoft.com/en-us/library/dd638205(v=exchg.150).aspx

Are the discovery and search arbitration mailboxes in

Free Windows Admin Tool Kit Click here and download it now
August 7th, 2015 8:49pm

Hi

Ok, I haven't made changes over the weekend and its working now.

Trying to figure out what changed on Friday to enable this

Thanks

August 11th, 2015 4:29am

Hi

This is only happening in PROD

Verbose switch ultimately provides the same result

Looks like all the rights are in place - Will look at it more carefully later today at some point

All required mailboxes are in place

Thanks

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2015 5:03am

Hi

This stopped working again, I got Microsoft onto the case and it turns out one of our mailboxes servers (we have 3) EWS "msExchInternalNLBBypassHostName" AD attribute value was incorrect. It was missing the port information. So

Incorrect URL https://mailbox01.domain.local/ews/exchange.asmx
Correct URL https://mailbox01.domain.local:444/ews/exchange.asmx

They then did an IISRESET across all mailbox servers and the search started working as expected.

They changed this via ADSI, Im not sure if or what the corresponding powershell command is.

Now just to find out why / who changed it

Thanks

August 11th, 2015 9:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics