MapiExceptionTooComplex when migrating one user's mailbox to Office 365.

We are moving from Exchange 2010 to Office 365, using a hybrid deployment. Most of our 50 users have migrated successfully, but we have one mailbox that keeps erroring when we start the mailbox sync. The error text is below, from the "MigrationErrors.csv" that downloads after the migration fails:

Error: Cannot query rows in a table. --> MapiExceptionTooComplex: Unable to query table rows. (hr=0x80040117, ec=-2147221225)

However, there is another error that happens during the migration, which I can get by downloading the details report on the migration batch for this user:

4/26/2016 3:56:13 PM [BLUPR0701MB2067] The Microsoft Exchange Mailbox Replication service 'BLUPR0701MB2067.namprd07.prod.outlook.com' (15.1.477.12 caps:03FFFF) is examining the request.
4/26/2016 3:56:13 PM [BLUPR0701MB2067] Connected to target mailbox 'BoxxTechnologiesInc.onmicrosoft.com\524acd2e-8c5c-42e7-befb-b4e08f651bfc (Primary)', database 'NAMPR07DG130-db050', Mailbox server 'BLUPR0701MB2067.namprd07.prod.outlook.com' Version 15.1 (Build 477.0).
4/26/2016 3:56:14 PM [BLUPR0701MB2067] Connected to source mailbox 'BoxxTechnologiesInc.onmicrosoft.com\524acd2e-8c5c-42e7-befb-b4e08f651bfc (Primary)', database 'DB01', Mailbox server 'BOXXEXCHANGE.iboxx.com' Version 14.3 (Build 279.0), proxy server 'BOXXExchange.iboxx.com' 14.3.227.0 caps:05FFFF.
4/26/2016 3:56:15 PM [BLUPR0701MB2067] Request processing continued, stage CreatingFolderHierarchy.
4/26/2016 3:56:15 PM [BLUPR0701MB2067] Stage: CreatingFolderHierarchy. Percent complete: 10.
4/26/2016 3:56:15 PM [BLUPR0701MB2067] Initializing folder hierarchy from mailbox 'BoxxTechnologiesInc.onmicrosoft.com\524acd2e-8c5c-42e7-befb-b4e08f651bfc (Primary)': 133 folders total.
4/26/2016 3:56:15 PM [BLUPR0701MB2067] Folder creation progress: 0 folders created in mailbox 'BoxxTechnologiesInc.onmicrosoft.com\524acd2e-8c5c-42e7-befb-b4e08f651bfc (Primary)'.
4/26/2016 3:56:56 PM [BLUPR0701MB2067] Transient error StoragePermanentException has occurred. The system will retry (2/900).

We're really at a loss as to what to do next. We've repaired the mailbox, and archived everything that we could find, to reduce the size of the mailbox, and we still can't get this mailbox to migrate. Because this is one of our main customer-facing addresses, we can't afford the downtime that would come with exporting the PST and importing it to Office 365.

Any help would be greatly appreciated.

Thanks!
Charles

This thread is locked. You can vote as helpful, but you cannot reply or subscribe to this thread.

Answer

RanMo_MSFT

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.
http://mfcmapi.codeplex.com/

Meanwhile, please try the following workaround and see if the move can be performed successfully.
1. 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
2. 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:FolderRestrictions
Start-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

Contribute to the Microsoft 365 and Office forum!

Subscription, account, billing Forum Top Contributors:

MapiExceptionTooComplex when migrating one user's mailbox to Office 365.

Replies (5)

Question Info

MapiExceptionTooComplex when migrating one user's mailbox to Office 365.

Replies (5) 

Question Info

Replies (5)