Home

Migration Endpoint problem 2010 to 2016 upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-1128061%22%20slang%3D%22en-US%22%3EMigration%20Endpoint%20problem%202010%20to%202016%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1128061%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20Exchange%202010%20Hybrid%20set%20up%20working%20just%20fine.%20All%20user%20mailboxes%20have%20been%20migrated.%20mail%20flow%20is%20happy.%20We%20still%20migrate%20a%20few%20new%20users%20each%20day%20(an%20old%20identity%20app).%20We're%20in%20the%20process%20of%20standing%20up%20Exchange%202016%20and%20retiring%20Exchange%202010%20and%20I%20ran%20into%20a%20problem%3A%3C%2FP%3E%3CP%3EI%20assume%20I%20need%20to%20run%20the%20Hybrid%20Config%20Wizard%20on%20my%20new%20Exchange%202016%20servers.%20It%20works%20for%20a%20while%20then%20hits%20an%20error%20and%20stops.%20In%20the%20log%2C%20the%20wizard%20just%20loaded%20up%20all%20the%20Migration%20Endpoints%20for%20testing%20and%20all%20I%20see%20after%20that%20are%20errors.%3C%2FP%3E%3CP%3EWhen%20i%20go%20to%20a%202010%20server's%20url%20https%3A%2F%2F%26lt%3B2010server%26gt%3B%2Fews%2Fmrsproxy.svc%20--%20i%20get%20notice%20about%20the%20service.%20so%20it%20returns%20something.%3C%2FP%3E%3CP%3EIf%20i%20try%20that%20on%20the%20new%20Exchange%202016%20server%2C%20i%20get%20nothing%3A%20http%20400%20error.%3C%2FP%3E%3CP%3EWe%20have%20a%20VIP%20for%20migrations%2C%20when%20its%20pointed%20at%202010%20it%20works%20fine.%20Mailboxes%20are%20migrated%20each%20morning.%20As%20soon%20as%20it%20is%20switched%20to%20the%20new%202016%20Exchange%20server%2C%20it%20never%20connects.%3C%2FP%3E%3CP%3EWhile%20logged%20into%20O365%20and%20VIP%20pointed%20at%202010%3A%3CBR%20%2F%3ETest-MigrationServerAvailability%20-ExchangeRemoteMove%20-RemoteServer%20mrsproxy.%3CMYDOMAIN%3E.com%20-Credentials%20%24Cred%3CBR%20%2F%3Eis%20sucessful%3C%2FMYDOMAIN%3E%3C%2FP%3E%3CP%3EPointed%20at%202016%3CBR%20%2F%3Ei%20get%20errors%3A%3CBR%20%2F%3EMicrosoft.Exchange.Migration.MigrationServerConnectionFailedException%3A%20The%20connection%20to%20the%20server%3CBR%20%2F%3E'mrsproxy.aafes.com'%20could%20not%20be%20completed.%20---%26gt%3B%3CBR%20%2F%3EMicrosoft.Exchange.MailboxReplicationService.MRSRemoteTransientException%3A%20The%20call%20to%3CBR%20%2F%3E'%3CA%20href%3D%22https%3A%2F%2Fmrsproxy.aafes.com%2FEWS%2Fmrsproxy.svc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmrsproxy.%3CMYDOMAIN%3E.com%2FEWS%2Fmrsproxy.svc%3C%2FMYDOMAIN%3E%3C%2FA%3E'%20failed.%20Error%20details%3A%20An%20error%20occurred%20while%3CBR%20%2F%3Ereceiving%20the%20HTTP%20response%20to%20%3CA%20href%3D%22https%3A%2F%2Fmrsproxy.aafes.com%2FEWS%2Fmrsproxy.svc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmrsproxy.%3CMYDOMAUIN%3E.com%2FEWS%2Fmrsproxy.svc%3C%2FMYDOMAUIN%3E%3C%2FA%3E.%20This%20could%20be%20due%20to%20the%3CBR%20%2F%3Eservice%20endpoint%20binding%20not%20using%20the%20HTTP%20protocol.%20This%20could%20also%20be%20due%20to%20an%20HTTP%20request%3CBR%20%2F%3Econtext%20being%20aborted%20by%20the%20server%20(possibly%20due%20to%20the%20service%20shutting%20down).%20See%20server%20logs%20for%3CBR%20%2F%3Emore%20details.%20--%26gt%3B%20The%20underlying%20connection%20was%20closed%3A%20An%20unexpected%20error%20occurred%20on%20a%20receive.%3CBR%20%2F%3E--%26gt%3B%20Unable%20to%20read%20data%20from%20the%20transport%20connection%3A%20An%20existing%20connection%20was%20forcibly%20closed%20by%3CBR%20%2F%3Ethe%20remote%20host.%20--%26gt%3B%20An%20existing%20connection%20was%20forcibly%20closed%20by%20the%20remote%20host.%20---%26gt%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EAutodicover%20has%20been%20moved%20to%20the%20new%202016%20server%20and%20works%20just%20fine.%20ECP%20on%20this%20new%202016%20server%20works%20just%20fine.%20I%20am%20missing%20somethign%2C%20but%20dont%20know%20exactly%20where%20to%20look.%3C%2FP%3E%3CP%3EThanks%20for%20any%20suggestions%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1128061%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eexchange%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%20issue%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Daniel Thompson
New Contributor

 

We have Exchange 2010 Hybrid set up working just fine. All user mailboxes have been migrated. mail flow is happy. We still migrate a few new users each day (an old identity app). We're in the process of standing up Exchange 2016 and retiring Exchange 2010 and I ran into a problem:

I assume I need to run the Hybrid Config Wizard on my new Exchange 2016 servers. It works for a while then hits an error and stops. In the log, the wizard just loaded up all the Migration Endpoints for testing and all I see after that are errors.

When i go to a 2010 server's url https://<2010server>/ews/mrsproxy.svc -- i get notice about the service. so it returns something.

If i try that on the new Exchange 2016 server, i get nothing: http 400 error.

We have a VIP for migrations, when its pointed at 2010 it works fine. Mailboxes are migrated each morning. As soon as it is switched to the new 2016 Exchange server, it never connects.

While logged into O365 and VIP pointed at 2010:
Test-MigrationServerAvailability -ExchangeRemoteMove -RemoteServer mrsproxy.<mydomain>.com -Credentials $Cred
is sucessful

Pointed at 2016
i get errors:
Microsoft.Exchange.Migration.MigrationServerConnectionFailedException: The connection to the server
'mrsproxy.<mydomain>.com could not be completed. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemoteTransientException: The call to
'https://mrsproxy.<mydomain>.com/EWS/mrsproxy.svc' failed. Error details: An error occurred while
receiving the HTTP response to https://mrsproxy.<mydomauin>.com/EWS/mrsproxy.svc. This could be due to the
service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request
context being aborted by the server (possibly due to the service shutting down). See server logs for
more details. --> The underlying connection was closed: An unexpected error occurred on a receive.
--> Unable to read data from the transport connection: An existing connection was forcibly closed by
the remote host. --> An existing connection was forcibly closed by the remote host. --->


Autodicover has been moved to the new 2016 server and works just fine. ECP on this new 2016 server works just fine. I am missing somethign, but dont know exactly where to look.

Thanks for any suggestions