none
Hybrid Deployment - Migrating from Exchange Online to On-Premise Exchange RRS feed

  • Question

  • Hi,

    I'm migrating from Exchange Online to an 2013 On-Premise Exchange. 

    Hybrid Deployment has been set up and configured successfully. 

    However, I'm encountering issues while performing a mailbox migration to the on-premise server. 

    It's has been stuck at validating and reflecting a MigrationTranscientException Error. 

    Appreciate the valuable advise and suggestions! Thanks!

    Cheers!

    Joshua

    Error message below:

    Data migrated: 
    Migration rate: 
    Error: MigrationTransientException: The Mailbox Replication Service could not connect to the remote server because the remote server encountered an internal error. The call to ‎'https://mail.domain.com.sg/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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> 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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error. --> The Mailbox Replication Service could not connect to the remote server because the remote server encountered an internal error. The call to ‎'https://mail.domain.com.sg/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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> 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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error. --> The call to ‎'https://mail.domain.com.sg/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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> 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>Runtime Error</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:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error


    • Edited by joshywahcho Tuesday, December 23, 2014 8:27 AM
    Tuesday, December 23, 2014 3:42 AM

All replies

  • Hi Joshywahcho,

    Please check that your MRSProxy is enabled ON-Premises.

    To do that

    1) Please type command below in Exchange Powershell for on-premise:

    Get-WebServicesVirtualDirectory "<servername>\EWS (Default Web Site)" *MRSProxyEnabled* 
    
    
    Set-WebServicesVirtualDirectory "<servername>\EWS (Default Web Site)" -MRSProxyEnabled $true
    

    2) Restart Microsoft Excange Mailbox Replication services

    3) Restart IIS service

    4) Make sure that you have input the correct "FQDN of the exchange replication service proxy", which should be public name of the mail server

    http://technet.microsoft.com/en-IN/library/dn155787(v=exchg.150).aspx


    Regards,

    Satyajit

    Please “Vote As Helpful” if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Tuesday, December 23, 2014 11:26 AM
  • Hi Satyajit,

    Thanks, My EWS was already enabled prior. I've just tried the steps you've suggested and attempting another migration now. The same error is popping up and status stuck at validating. Is there anything to do with this?

    "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)‎."

    Regards,

    Joshua

    Wednesday, December 24, 2014 3:35 AM
  • Please disable in-place hold, and wait for about several hours, and try to move the mailbox from Exchange Online to on-premises Exchange server.

    If you still cannot move the mailbox from Exchange Online to on-premises after disabling in-place for several hours, you can run the command get-mailbox -identity | fl *hold*

    Regarding the issue that you cannot move the mailbox which is not enabled Archive or in-place hold from Exchange Online to on-premises Exchange server, the issue is different from the original issue.


    Dinesh S.

    Wednesday, December 24, 2014 4:02 AM
  • Hi Dinesh,

    I've checked and in-place hold is not enabled. There isn't anything configured to be on hold too.

    Any other advice?

    Regards,

    Joshua

    Friday, December 26, 2014 2:43 AM
  • Hello Joshywahcho ,<o:p></o:p>

    First Check  is the MRS proxy is enabled or not and restart the Microsoft Exchange Mailbox Replication service and IIS on Hybrid .<o:p></o:p>

    As now Microsoft has change the procedure to roll back the mailbox from O365, please follow the below mention Step<o:p></o:p>

    Moved the affected user's mailbox to the Hybrid Server from Office 365 <o:p></o:p>

    ·         Connect to Exchange Online using remote PowerShell<o:p></o:p>

    ·         Ran the command $Credentials = Get-Credential<o:p></o:p>

    ·         Ran the command New-MoveRequest -identity <e-mail address of the affected user> -OutBound -RemoteTargetDatabase "Name of the Datbase" -RemoteHostName <Your Host Name> -RemoteCredential $Credentials -TargetDeliveryDomain <Your Target Delivery Domain><o:p></o:p>

    ·         Ran the command Get-MoveRequest -Identity <e-mail address of the user> to check the status of mailbox move<o:p></o:p>

    ·         once the mailbox move from Office 365 to Hybrid Server was completed then initiated a Mailbox move from the Hybrid Server to On-premise server <o:p></o:p>

    ·         Mailbox was moved successfully from Hybrid Server to the On-premise server .<o:p></o:p>

    ·         checked in the On-premise server 2007 and the affected user's mailbox was showing there<o:p></o:p>


    Saturday, April 25, 2015 3:43 AM