Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Cross Forest Migration: mrsproxy.svc' failed because no service was listening on the specified

$
0
0

I am running a Cross Forest Migration from Exchange 2010  SP3 to Exchange 2013

I have

  • Two-way Trust in place
  • Enabled MRS Proxy on the Source Client Access Servers
  • Increase timeout in the Exchange 2010 web.config files and restarted IIS
  • Exported the Cert from Source Exchange Server and import it on Target Exchange Server

I run the following prepare move command

.\Prepare-MoveRequest.Ps1 -Identity "EMAIL ADDRESS" -RemoteForestDomainController "SOURCE DC" -RemoteForestCredential $Remote -LocalForestDomainController "CHILD.TARGET DC" -LocalForestCredential $Local -TargetMailUserOU "OU=x DC=com" –UseLocalObject

This runs then I run ADMT to migrate the password and SID History.

Then I run the following Move Request

New-MoveRequest -Identity "EMAIL ADDRESS" -Remote -TargetDatabase "DB" -RemoteGlobalCatalog " SOURCE DC" -RemoteCredential $Remote -TargetDeliveryDomain "SMTP DOMAIN"-RemoteHostName outlook.company.com -DomainControllerCHILD.TARGET DC

 

Now I get the following error message:

The call to 'https://outlook.company.com/EWS/mrsproxy.svc' failed because no service was listening on the specified

endpoint. Error details: There was no endpoint listening at https://outlook.company.com/EWS/mrsproxy.svc that could

accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for

more details. --> The remote server returned an error: (404) Not Found.

From the Target Exchange server I can browse to 'https://outlook.company.com/EWS/mrsproxy.svc' and enter my credentials and it connects.

I am using a F5 Load Balancer in the Source domain so on the Target domain Exchange server where I am running the command I edit the Host file so outlook.company.com points to the Source CAS server IP, but I still get the exact same error.

Any ideas please !! 


Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>