Error 11:
Failed to find a principal in the target forest that corresponds to a source/target forest principal ( A corrupted item was encountered: Folder ACL “Foldername").
Fix:
This message is related to mailbox/mailboxfolder permissions that cannot be migrated, since cloud MRS service cannot find the object from permissions list in the destination forest, to map these permissions against.
Fix: See below article for more details:
https://blogs.technet.microsoft.com/exchange/2017/05/30/toomanybaditemspermanentexception-error-when-migrating-to-exchange-online/
Error 12:
Cannot query rows in a table. --> MapiExceptionMaxObjsExceeded: Unable to query table rows.
FailureType : StoragePermanentException
Fix:
Increase limit of Search Folders in the on-premises Exchange Server as per below steps:
1.On the Exchange server hosting the target database where cloud mailbox will be offboarded, look for and open the following config file:
Microsoft.Exchange.Store.Worker.exe.config, found in Bin folder of %ExchangeInstallPath% .
2.Add the following lines in Configuration tag, between </runtime> and </configuration>
<appSettings>
<add key="DynamicSearchFolderPerScopeCountReceiveQuota" value="250" />
</appSettings>
3.Restart Microsoft Exchange Information Store service after modifying this file and try again the move.
Error 13:
The call to 'https://MRSPROXYHOST/EWS/mrsproxy.svc SERVER.domain.com (14.3.178.0 caps:05FFFF)' failed.
Error details: The remote endpoint no longer recognizes this sequence. This is most likely due to an abort on the remote endpoint. The value of wsrm:Identifier is not a known Sequence identifier. The reliable session was faulted.
FailureType:CommunicationErrorTransientException.
Additional Information:
This error is usually caused by a wrong load-balancer configuration, when using multiple Exchange 2010 CAS servers.
Fix:
To prevent this issue, make sure that your load-balancer is keeping the session affinity/persistence. This behavior is explained in the next article:
https://blogs.msdn.microsoft.com/brad_hughes/2017/02/21/its-always-the-load-balancer/
Error 14:
MissingExchangeGuidException: The user object for *** Email address is removed for privacy ***' does not have a valid ExchangeGuid property and cannot be migrated.
This issue occurs when EXO fails to provision the ExchangeGUID attribute for an user(msoluser will have a validation error), because this ExchangeGUID value is already used by another object from EXO, it could be an active mailbox/mailuser or a soft deleted mailbox/mailuser.
Fix:
First use this command to get the ExchangeGUID/ArchiveGUID from the validation error:
(Get-MsolUser -UserPrincipalName *** Email address is removed for privacy ***).errors.errordetail.objecterrors.errorrecord| fl
Search in EXO PowerShell for the object that is using the mentioned EXchangeGUID or ArchiveGUID:
Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value'|ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*
Once you found the object that is using this guid, you have to purge it:
1.If it is a softdeleted MailUser: Remove-MailUser 'ExchangeGUID value' -PermanentlyDelete
2.If it is a softdeleted UserMailbox, run: Remove-Mailbox 'ExchangeGUID value' -PermanentlyDelete
-if this command fails due to mailbox being protected by hold, you have to disable the hold first(check if data backup is required):
Set-Mailbox *** Email address is removed for privacy *** -LitigationHoldEnabled $false -InactiveMailbox
3. If it turns to be an active mailuser/mailbox that is using this ExchangeGUID/ArchiveGUID, you need to evaluate the option to purge that user(however, this is a very rare scenario though).
4. After the faulty object has been purged from EXO, we need to fix the validation error by forcing the object provisioning:
Get-MsolUser -UserPrincipalName *** Email address is removed for privacy *** |fl *objectID*
Redo-MsolProvisionUser -ObjectId 'paste the *objectID* value from above command'
5. After 5 minutes run this command to confirm if your validation error is fixed:
(Get-MsolUser -UserPrincipalName *** Email address is removed for privacy ***).errors.errordetail.objecterrors.errorrecord| fl
6. If the validation error is gone, you can try again the migration.
Error 15:
The call to 'https://<ServerName>/EWS/mrsproxy.svc' failed. Error details: Access is denied” error when you try to create a new migration batch or to start a new move request, using Exchange 2013 as the migration server.
Additional Information:
This issue occurs if the computer account of the Exchange 2013 hybrid server is a member of one or more protected groups.
Fix:
Error 16:
The call to 'https://mail.contoso.com/ews/mrsproxy.svc' failed. Error details: Unable to cast object of type 'System.String' to type 'System.String[]'.. --] Unable to cast object of type 'System.String' to type 'System.String[]'.FailureType:CommunicationErrorTransientException
Additional Information:
This error can be caused by some restrictions or invalid properties on the "Search Folders" defined by the user.
Fix:
Start Outlook client from where the affected user profile is configured, using the switch "outlook.exe /cleanfinders
Error 17:
The call to 'https://mail.contoso.com/ews/mrsproxy.svc' failed. Error details: Unable to cast object of type 'System.String' to type 'System.String[]'.. --] Unable to cast object of type 'System.String' to type 'System.String[]'.FailureType:CommunicationErrorTransientException
Additional Information:
This error can be caused by some restrictions or invalid properties on the "Search Folders" defined by the user.
Fix:
Start Outlook client from where the affected user profile is configured, using the switch "outlook.exe /cleanfinders", and re-attempt the migration.
Error 18:
Target database 'xxxx-xxxx-xxxx-xxxx' cannot be used: Database is excluded from provisioning: 'True'.
Additional Information:
This error can occur when the migration service is assigning you a target database that might be under maintenance work.
Fix:
The fastest solution is to delete the affected move request and to start a new one, in order for the migration service to select a new database.
Error 19
Failuretype: MailboxIsNotInExpectedMDBPermanentException /Error Message: The mailbox is in not in the expected mailbox database.
Fix:
This error can be expected when for example the source/target database has failed over another database during the remote move request.
Usually this error can be fixed when you resume the moverequest. If the error persists, you can try moving the affected mailbox to another local database, then to start a new move request to Exchange Online.
Error 20:
FailureType: StoragePermanentException . Error Message: Cannot save changes made to an item to store. --> MapiExceptionMaxObjsExceeded: Unable to save changes.
Fix:
This error is usually related to the max number of items from a mailbox folder being reached ( >1 million items).
In order to find the folder in question(it can be a folder under IPM subtree or from outside IPM), you can run below commands:
$root=Get-MailboxFolderStatistics -Identity *** Email address is removed for privacy ***
$root|sort itemsinfolder -descending |ft folderpath,itemsinfolder
$non_root=Get-MailboxFolderStatistics *** Email address is removed for privacy *** -FolderScope NonIpmRoot
$non_root|sort itemsinfolder -descending |ft folderpath,itemsinfolder
If the faulty folder is accessible from Outlook/MFC MAPI, then you can move some of the items to other folders, to have under 1 mil items per folder and resume the migration.
If this folder is a non IPM folder, for example "/" root folder, there is no easy way to access the items from it and the best option would be to export the mailbox content into a PST file
and import it in the remote mailbox, after following this article: https://support.microsoft.com/en-us/help/2745710/a-user-can-t-access-a-mailbox-by-using-outlook-after-a-remote-mailbox
Comments
0 comments
Please sign in to leave a comment.