Microsoft Knowledge Base Email Alertz

Mailbox move from Exchange 2007 to Exchange 2010 fails with error Unable to synchronize manifest”

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 2221826 - Last Review: September 7, 2010 - Revision: 6.0

Mailbox move from Exchange 2007 to Exchange 2010 fails with error "Unable to synchronize manifest”

Symptoms

Migration to Exchange 2007 "staging" server is successful, however when later a mailbox is moved to Exchange 2010 the following Exchange error is received:

Error: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233)
Diagnostic context:
Lid: 18969 EcDoRpcExt2 called [length=149]
Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=371][latency=15]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropOpenFolder [2]
Lid: 27962 ROP: ropIncrCfg [112]
Lid: 27962 ROP: ropUpldStStrmBegin [117]
Lid: 27962 ROP: ropUpldStStrmEnd [119]
Lid: 27962 ROP: ropUpldStStrmBegin [117]
Lid: 27962 ROP: ropUpldStStrmEnd [119]
Lid: 27962 ROP: ropUpldStStrmBegin [117]
Lid: 27962 ROP: ropUpldStStrmEnd [119]
Lid: 27962 ROP: ropUpldStStrmBegin [117]
Lid: 27962 ROP: ropUpldStStrmEnd [119]
Lid: 27962 ROP: ropFXSrcGetBufferEx [156]
Lid: 17082 ROP Error: 0x8004010F
Lid: 23137
Lid: 21921 StoreEc: 0x8004010F
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 26426 ROP: ropFXSrcGetBufferEx [156]
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F10003
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F10003
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67F10003
Lid: 23921 StoreEc: 0x3EC
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040
Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67A40014
Lid: 7155 StoreEc: 0x8004010F
Lid: 7155 StoreEc: 0x8004010F
Lid: 6131 StoreEc: 0x8004010F
Lid: 2238 StoreEc: 0x8004010F
Lid: 1750 ---- Remote Context End ----
Lid: 26849
Lid: 21817 ROP Failure: 0x8004010F
Lid: 32758
Lid: 16586 StoreEc: 0x8004010F
Lid: 22518
Lid: 28874 StoreEc: 0x8004010F
Lid: 29516
Lid: 31820 StoreEc: 0x8004010F

Cause

This is a known issue with mailboxes previously migrated to Exchange Server 2007 using Quest Migration Manager (QMM) version 8.5.  According to the Quest support site, this is resolved in the next release of QMM, version 8.6.

Resolution

The resolution can be found at the Quest support site:
 
Mailbox move from Exchange 2007 to Exchange 2010 fails with error "Unable to synchronize manifest"
 
Note:  You may need to either logon or register on the Quest site to access this information.
 
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

More Information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
Keywords: 
KB2221826
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate