Mailbox move - "TooManyMissingItemsPermanentException"

I'm performing a migration from Exchange 2007 to 2013, and have got to the stage of moving mailboxes across to the new server.  The first few mailboxes I migrated transferred across with no problems, but I've encountered one which fails with the error "TooManyMissingItemsPermanentException":

Powershell screenshot
The post by Maciej Korman at http://community.office365.com/en-us/forums/156/t/205777.aspx suggests that changing the ContentVerificationMissingItemThreshold parameter in the "C:\Program Files\Microsoft\Exchange Server\V15\Bin\MsExchangeMailboxReplication.exe.config" file might do the trick, but I wasn't able to make this work, nor was I able to find any documentation on this.

Any ideas how I might proceed, please?
LVL 1
wakatashiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

pcmghouseCommented:
You can specify the # for skipped corrupted items.
More Options/Bad Item Limit available in the Migration Console should help you.

The Bad Item Limit can be picked from the migration report of your failed mailbox.
0
wakatashiAuthor Commented:
Hi pcmghouse,

It seems to be making a distinction between "missing items" and "bad items".  I've tried setting the "bad items" limit to (for example) 100, but actually it's reporting that it hasn't come across anything that's defined as a "bad item" - you can see on my screenshot that it says "BadItemsEncountered: 0".

What do you think?
0
wakatashiAuthor Commented:
I've found out how to identify the items it has a problem with.  In the Exchange Management Shell, type:

get-moverequest -identity <user's identity> |get-moverequeststatistics -includereport |fl

That'll tell you where the problematic items are in the user's folder hierarchy.  They can then be deleted before trying again with the move.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

wakatashiAuthor Commented:
Found a solution myself.
0
teksouthCommented:
care to share your solution?
0
wakatashiAuthor Commented:
It's the post above yours marked "Accepted Solution".
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.