Forum Discussion
Exchange online migration fails with various errors
Hi All,
Exchange 2016 to online some mailboxes are failing with various errors but some are migrating. Below are the errors
This user is in failed state
SourceMailboxConnectionStalePermanentException: Couldn't connect to the source mailbox. --> The call to 'https://9e37dad4-35f4-4b69-9b66-e0244b237802.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed. Error details: The remote server returned an unexpected response: (302) Found. --> Too many automatic redirections were attempted.. --> The remote server returned an unexpected response: (302) Found. --> Too many automatic redirections were attempted.
This error user is in Synced state
Error: CommunicationErrorTransientException: The call to 'net.tcp://ve1pr08mb5600.eurprd08.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService VE1PR08MB5600.eurprd08.prod.outlook.com (15.20.7939.10 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)' failed. Error details: The Mailbox Replication Service could not connect to the remote server because the remote server encountered an internal error. The call to 'https://9e37dad4-35f4-4b69-9b66-e0244b237802.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed. Error details: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html> <html> <head> <title>User agent string cannot be null or empty<br>Parameter name: userAgent</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:pointer; } @media scre'. --> The remote server returned an error: (500) Internal Server Error.. --> The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html> <html> <head> <title>User agent string cannot be null or empty<br>Parameter name: userAgent</title> <meta name="viewport" content="width=device-width" /> <style> body {font-
Fatal error TooManyTransientFailureRetriesPermanentException has occurred.
I have reinstall the modern hybrid agent and set the MRS proxy settings and etc. Still the same issue.
5 Replies
- Seeing this week all of a sudden that offboard migrations aren't working for us. Similar error except our migration endpoint is fine, works for onboarding and passes with "SUccess" on the Test-MigrationServerAvailability in EXO PowerShell
"rror: CommunicationErrorTransientException: The call to 'net.tcp://yt2pr01mb10469.canprd01.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService YT2PR01MB10469.CANPRD01.PROD.OUTLOOK.COM (15.20.8069.20 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)' failed. Error details: . -->"- Jeremy,
try to reinstall the agent. It will fix the issue.
Have to done any changes to MRS configuration file?Sankaperera thanks for the tip. My issue ended up being super simple and the on-prem object's ExchangeGuid needed to be set to match the EXO mailbox'. This problem used to get a nice and easy error message but now gets this new odd and unhelpful one. Nonetheless I was stung by my own weak blinders.
- I have the same issue. Were you able to find a fix?
- yes, did you change any values relate to MRSconfiguration file?
