Known solutions for hybrid migrations errors

Some known O365 migration errors and their solutions are mentioned below:

Error 1: MigrationPermanentException: You must specify the PrimaryOnly parameter.

Possible reason: This error can occur when you attempt to migrate to cloud an on-prem mailbox via a migration batch from EAC, where the online archive already exists for this user.

Fix: In order to migrate the primary mailbox to Office 365, you will need to start the mailbox move with the following command, from Exchange Online PowerShell: New-MoveRequest –Identity <user> -RemoteCredential (Get-Credential) -Remote -RemoteHostName 'mail.contoso.com' -TargetDeliveryDomain <tenant.mail.onmicrosoft.com -PrimaryOnly

Error 2: Couldn't switch the mailbox into Sync Source mode. This could be because another administrator is currently moving the mailbox into the destination database, the mailbox is locked, or the Microsoft Exchange Mailbox Replication service doesn't have the correct permissions. FailureType: SourceMailboxAlreadyBeingMovedTransientException.

This above error can also be correlated with slow migration performance.

Possible solutions:

-Check if there is any local move request for this user on the on-prem Exchange Server.

-In case you have Exchange 2010 with multiple CAS servers that are load balanced, make sure that your Load Balancer maintains the session affinity, more exactly all the incoming migration requests for a mailbox should be processed by the same CAS server.

-Try to see if setting the TCP KeepAliveTime on the server hosting the source mailbox to 5 minutes (instead of 2 hours) will fix the issue. More details can be found in this article:

https://blogs.msdn.microsoft.com/brad_hughes/2016/12/16/source-mailbox-already-being-moved-errors-while-moving-mailboxes/

Error 3: Failed to convert the source mailbox 'mailboxID' to mail-enabled user after the move.
FailureTpe: UpdateMovedMailboxPermanentException.

- There is a property named AdminCount on each user in local AD, that by default is not populated or it gets set to “1”, once an account is added to a privileged group.
- The AdminCount value has no effect on the account and is used as a flag to indicate the account is, or was, protected.
- The user might end up with 2 mailboxes: 1 in local Exchange and 1 in EXO.
- More information about inherited AD permissions can be found in this article:
https://blogs.msdn.microsoft.com/muaddib/2013/12/30/how-to-modify-security-inheritance-on-active-directory-objects-using-powershell/ 

Fix:
https://support.microsoft.com/en-us/help/2745710/a-user-can-t-access-a-mailbox-by-using-outlook-after-a-remote-mailbox-move-from-an-on-premises-exchange-server-environment-to-office-365 

Error 4: MapiExceptionTooComplex: Unable to query table rows. (hr=0x80040117, ec=-2147221225)

Fix:
To prevent this failure during the move process (onboarding or offboarding) you need to skip moving the folder views or folder restrictions along with the mailbox, by starting the move from EXO PowerShell as below:
New-MoveRequest –Identity *** Email address is removed for privacy *** -SkipMoving: FolderViews, FolderRestrictions -Remote -RemoteCredential(Get-Credential)-RemoteHostName "mrsproxy.contoso.com" -TargetdeliveryDomain contoso.com

Error 5: MigrationPermanentException: You can’t use the domain because it’s not an accepted domain for your organization. –> You can’t use the domain because it’s not an accepted domain for your organization. 

Fix:

Check on the AD user object if there are any proxy addresses in some domains that are not verified in Exchange Online. Once you identified the faulty email addresses, remove them and force the AADconnect sync. Then start a new migration for the affected user.

Error 6: MigrationPermanentException: The target mailbox doesn’t have an SMTP proxy matching ‎'contoso.mail.onmicrosoft.com‎'

This issue may occur if the source mailbox isn't stamped with a <domain.mail.onmicrosoft.com> SMTP address.

Fix:

https://support.microsoft.com/en-gb/kb/2939340 

Error 7: MigrationPermanentException: Cannot find a recipient that has mailbox GUID <GUID>" error message when you try to move a mailbox in an Exchange hybrid deployment.

This behavior occurs because the value of the ExchangeGUID attribute from Exchange Online user isn't stamped on the associated remote mailbox from the on-premises organization.

Fix:

https://support.microsoft.com/en-us/kb/2956029 

Error 8: Fatal error TooManyMissingItemsPermanentException has occurred.
or Fatal error TooManyBadPermanentException has occurred.

This issue can occur because the bad items limit for the move request has been reached.

Fix:

In order to fix the issue, you should increase the bad items limit to a higher value:
Set-MoveRequest <user> –BadItemLimit 100
Resume-MoveRequest <user>

Error 9: The call to 'https://mail.contoso.com/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out attempting to send after 00:00:00.
Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.
or
The call to 'https://mail.contoso.com/EWS/mrsproxy.svc' failed because no service was listening on the specified endpoint.
Error details: There was no endpoint listening at https://mail.contoso.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.

These errors are usually occurring only for particular users, while other mailboxes can be moved successfully. They are caused by the ExchangeGuid mismatch between EXO and local Exchange:

Fix:

https://support.microsoft.com/en-us/topic/-the-remote-server-returned-an-error-404-or-http-request-has-exceeded-the-allotted-timeout-error-when-you-move-a-mailbox-from-on-premises-exchange-server-to-exchange-online-04f3586e-d52e-5fbb-093a-03dc9a34cd8d 

Error 10: The call to ‘https://mail.domain.com/EWS/mrsproxy.svc ‘ failed. Error details: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults
(either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.. –>
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)
on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

The failure type for this error is CommunicationErrorTransientException.

This error is caused by some particular folders views from source mailbox. MRS fails to create these folders into the hierarchy of the destination mailbox.

Fix:

https://blogs.technet.microsoft.com/latam/2016/01/05/o365-error-when-trying-to-move-a-mailbox-to-the-cloud-creatingfolderhierarchy-communicationerrortransientexception/ https://support.microsoft.com/en-us/help/3063045/-transientexception-errors-when-you-try-to-move-mailboxes-from-exchange-online-to-exchange-server-2007-in-the-on-premises-environment