Hi Charles,
Thanks so much for the logs you sent to me. What you understood is correct, the move stopped when creating folder hierarchy. And from the log, I found the following information.
Operation: IDestinationMailbox.CreateFolder
Operation: IDestinationMailbox.CreateFolder
OperationSide: Target
Boxxxxx.onmicrosoft.com\524acd2e-8c5c-42e7-befb-b4e08f651bfc (Primary)
Folder: 'Sent Items', entryId
[len=46,data=000000000F0C2CA9F277564A8D32A6B6548EE2FB010007FA93F29F162242B8D3BE6DF4DB6C9B0000016374F60000],parentId [len=46,data=000000000F0C2CA9F277564A8D32A6B6548EE2FB010007FA93F29F162242B8D3BE6DF4DB6C9B0000016374F10000]
CreateFolderFlags: None
Folder: '/Top of Information Store/Sent Items', entryId
[len=46,data=000000000F0C2CA9F277564A8D32A6B6548EE2FB010007FA93F29F162242B8D3BE6DF4DB6C9B0000016374F60000], parentId
[len=46,data=000000000F0C2CA9F277564A8D32A6B6548EE2FB010007FA93F29F162242B8D3BE6DF4DB6C9B0000016374F10000]
It indicates that the error appeared when it was creating the Sent Items folder. To identify the root cause, please download the MFCMAPI and have look at the sent items folder.
Meanwhile, please try the following workaround and see if the move can be performed successfully.
- Removing and recreating the faulty folder using MFCMAPI (in this case only sent items folder):
a. Disable single item recovery, litigation hold or in-place hold if any of them are enabled
b. Move all items out of the Sent items folder to somewhere else
c. Connect to the mailbox using MFCMAPI with the "Use MDB_ONLINE when calling OpenMsgStore" option enabled (see http://support.microsoft.com/kb/2509983/en-us )
d. Delete the sent item folder using MFCMAPI, with the "Hard Deletion" option. You will get an error message (if it's a system folder), and when you refresh your view the folder will still be there
e. Move all the items back into the folder
f. Re-enable single item recovery / hold if required
g. The move request should now work successfully
- Create a migration batch for this user in the Exchange Online powershell and use the –SkipMoving:FolderRestrictions parameter in order to skip the unsupported restrictions:
$OnboardingBatch = New-MigrationBatch -name "Batch_name" -SourceEndpoint MigrationEndpointName -TargetDeliveryDomain domain.mail.onmicrosoft.com -SkipMoving:FolderRestrictionsStart-MigrationBatch -Identity $OnboardingBatch.Identity
If the above workaround still cannot provide you a successful move request, please try repair the move request via the cmdlet below and update us the results.
New-MailboxRepairRequest -Mailbox xxx–CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview
Best regards,
Ran