Move mailbox fails from exchange 2010 to 2013

I'm in the last phase of migrating from exchange 2010 to 2013.  Over the weekend I was able to move approximately 1250 mailboxes from 2010 to 2013.  There are two mailboxes that refuses to move (both shared mailboxes).

Deleting the request and creating a new one gets the same error.  It will run for 12 to 18 hours then fail with the following error (mailbox is only 200 megs in size so it shouldn't take that long).

Data migrated: 305.2 KB ¿(312,540 bytes)¿
Migration rate: 0 B ¿(0 bytes)¿
Error: MigrationPermanentException: Error: Cannot query rows in a table. --> MapiExceptionInvalidObject: Unable to query table rows. ¿(hr=0x80040108, ec=-2147221240)¿ Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=1569] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=403][latency=77] Lid: 52176 ClientVersion: 15.0.712.17 Lid: 50032 ServerVersion: 15.0.712.6014 Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropGetContentsTableExtended [164] Lid: 27962 ROP: ropSetColumns [18] Lid: 27962 ROP: ropRestrict [20] Lid: 17082 ROP Error: 0x80040108 Lid: 27489 Lid: 21921 StoreEc: 0x80040108 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 65304 StoreEc: 0x8004010F Lid: 58880 StoreEc: 0x80040108 Lid: 63016 dwParam: 0x14 Lid: 39640 StoreEc: 0x80040108 Lid: 10786 dwParam: 0x0 Msg: 15.00.0712.012:SHB-EXGDB3 Lid: 1750 ---- Remote Context End ---- Lid: 27962 ROP: ropQueryRows [21] Lid: 17082 ROP Error: 0x80040108 Lid: 17153 Lid: 21921 StoreEc: 0x80040108 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 65304 StoreEc: 0x8004010F Lid: 58880 StoreEc: 0x80040108 Lid: 63016 dwParam: 0x14 Lid: 39640 StoreEc: 0x80040108 Lid: 10786 dwParam: 0x0 Msg: 15.00.0712.012:SHB-EXGDB3 Lid: 60464 dwParam: 0x80040108 Lid: 10786 dwParam: 0x0 Msg: 15.00.0712.012:SHB-EXGDB3 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80040108 Lid: 28414 Lid: 32510 StoreEc: 0x80040108

I can move the mailbox between 2010 databases easily, takes about 10 minutes. but moving it to 2013 has been unsuccessful.

any clue what is causing the failure and how to work around it?  thanks
Who is Participating?
peter_fieldConnect With a Mentor Commented:
Yeah, our MS ticket went nowhere as well. Thanks for the suggestion, I actually wrote up a script to try a migration for every possible combination of 2010<->2013 servers, and not one combination worked unfortunately (that was 48 combinations, yes, I'm desperate).

I might give the backup/restore option a shot, but that is basically as much work and around the same level of disruption for the end users so other than keeping the dumpster/rules/other bits doesn't save much, and has the risk it will result in the same error anyway.

We still have more than 50,000 accounts to migrate, I'm expecting to get quite a lot of these before we are done, and between trying to minimize disruption, ensuring mail delivery during the fix and not stuffing anything up like rules or X500 addresses this is going to drive me insane.

Thanks for your help.
Seth SimmonsSr. Systems AdministratorCommented:
if it's only 2 mailboxes and if they aren't that big then might be best just to export to pst, remove the mailbox from 2010 and create a new one on 2013 and import
NIS_RULEAuthor Commented:
That would be my last option.  These two mailbox aren't that big (about 1.5gb each) but the mailboxes are shared mailboxes so lots of different shared permissions.  I'd hate to have to set all that up again and contact all the end users to make sure they still have all the proper access.

If there was a way to get them to migrate over that would be ideal
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Seth SimmonsSr. Systems AdministratorCommented:
you said before the mailbox is only about 200mb
NIS_RULEAuthor Commented:
the live data is about 200MB but once you add all the recoverable deleted items, it is about 1.5GB.  Ideally I'll like to preserve that (which you can't do with an export to pst).
Have you made any progress on this? We are having the same issue. So far I have been doing the export/new mailbox/import business which is very frustrating as I can see you are aware.
NIS_RULEAuthor Commented:
yes, what finally worked for us is to migrate the mb that is having issues to another database on 2010, (may have to do this 2 or 3 times) then migrate it to 2013.  That worked for us on the mailboxes that were having issues.
No such luck for us unfortunately. It was worth a shot, thanks for sharing.
NIS_RULEAuthor Commented:
Have you tried to migrate the 2010 mailbox to a few different 2010 databases, then migrate it to a few different 2013 databases?  That's what worked for us.  We eventually found a combination of 2010 db -> 2013 db that worked.

I had opened a ticket with MS and worked with them for 2 weeks straight on it and they couldn't figure it out.  After two weeks, they gave up and suggested I export to PST then re-import.

Another solution I found on a different forum is to backup the 2010 db on whatever backup software you use.  Delete the online mailbox,  restore the backup to a different 2010 database, then migrate it to a 2013 db.  I was going to try this next if moving to different 2010 db's didn't work for us.  but didn't have to try this. so you can give it a shot
OK. I have narrowed it down, and have successfully fixed a number of mailboxes now. I still do not have root cause, or a direct fix.

If you do the following once the move request goes into "TransientFailure" it will give you the item/folder that has the issue:
(Get-MoveRequestStatistics <yourmailbox> -IncludeReport).Report.Failures | select -expand datacontext

Open in new window

In every one of our cases, it has been the "Sent Items" folder. The way I've got the mailboxes to move is:
Disable single item recovery, litigation hold or inplace hold if any of them are enabled
Move all items out of the folder to somewhere else
Connect to the mailbox using MFCMAPI with the "Use MDB_ONLINE when calling OpenMsgStore" option enabled (see
Delete the 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
Move all the items back into the folder
Re-enable single item recovery / hold if required
The move request now works successfully

This is a decent pain, but in my opinion better than export/import as there is no data loss other than maybe some settings on the folder in question. If you're using retention tags and it's a non-system folder, I'd be checking that the tag remained. I did notice some settings I would have thought would be on the folder persisted, so maybe it doesn't actually delete the folder, just fixes whatever is wrong with it.

Unless I get a lot more of these, I'm not going to dig into exactly what is wrong with the folder itself, but hopefully if you are after that, this should give you enough to track it down to that level if you want.

Some other points I noticed:
Every single one of the failed mailboxes we have had have been shared mailboxes, I'm not sure how that fits into the equation, but I'm sure it is a factor. I suspect something with DelegateSentItemsStyle as it is set on the clients accessing every one of the affected mailboxes.
The DataContext from the move request statistics shows Exchange trying to apply folder restrictions on the target has a very interesting filter. The filter seems to point to a specific item, but finding and removing the item from the mailbox does not fix the issue
Doing an export of the properties of the folder before and after deleting it with MFCMAPI shows no differences at all, whatever is fixing the issue presumably is happening somewhere else in the store other than the folder itself
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.