When performing a move request, an error occurs.
This specific example is for TransientFailureTarget, but this can work with any error.
This error occurs with using both Powershell and the Office365 admin console.
The error will also appear in the migration report, but looks like:
Couldn't find a move request that corresponds to the specified identity 'TuftsCloud.onmicrosoft.com\54958b7d-d54e-4533-ac11-da48fea53fdc'. --> Couldn't find a move request that corresponds to the specified identity 'TuftsCloud.onmicrosoft.com\54958b7d-d54e-4533-ac11-da48fea53fdc'. |
To investigate this further, generate a report using Powershell. You must do this while the request still exists, so do not remove the request until you have generated the report!
Get-MoveRequestStatisctics -Identity <UTLN> -IncludeReport | fl
The culprit that we are looking for is:
10/3/2016 9:05:14 PM [BL2PR05MB2195] Transient error CommunicationErrorTransientException has occurred. The system will retry (1/620).
Generate an XML report and filter the errors:
$stats = Import-CliXml report.xml
$stats.report.failures[-1]
*NOTE: This might have to be generated by running Powershell as Admin*
The DataContext of the report will give us what we want.
Example:
Search folder: '/Finder/OwaFV15.1MentionedAAMkADc0MmYzOTJmLTU1NmUtNDdjNC05MjMxLTFhMGVlOWUzYjAwMgAuAAAAAADwkF5wX0ujTa8swMmlw6CPAQB2Lw0MIn9cRo0WKRIM7ckNAAAAAAENAAA='
This tells us where the problem is. A search folder called /Finder/OwaFV15
Download and installed the MFCMAPI program.
This only analyzes local profiles.
Before launching MFCMAPI, make sure you provide your admin exchange account with access (full permission) to the users mailbox.
Set up a local profile using your admin exchange account (if not setup yet) as well.
When launching MFCMAPI, select Session -> Logon...
Select your admin mail profile, and you will see a list of all the mailboxes that you have access to.
Double-clicking on the appropriate mailbox will open another window.
Expanding the drop down on the left gives you a list of all properties.
Locate the one in question from the report - /Finder/OwaFV15
This time there were multiple folders that matched up, since just one wasn't called OwaFV15.
Right clicking on the folders and select Advanced -> Reset permissions on folder contents should resolve the migration issue.
If not, then delete the tables instead. They will be recreated once the mailbox is migrated and the user logs in for the first time.
Once all of this has completed, you can delete the mailbox move request and start another one.
This time there should be no errors, but if there are use the above steps to determine where the migration is failing.
References:
MFCMAPI: https://mfcmapi.codeplex.com/