none
Failed to reset the target mailbox after the move. Attempt 1/6.

    Question

  • Hi,

    After a move of a mailbox on Exchange 2010 to another DB, we've got the following error:

    .
    .

    1-10-2013 13:53:47 [EX02] Move has completed and final clean up has started.
    1-10-2013 13:53:47 [EX02] Source mailbox 'Primary (ed4afffb-e2aa-4488-be1d-6950af50159a)' was successfully cleaned up after the move.
    1-10-2013 13:53:47 [EX02] Failed to reset the target mailbox after the move. Attempt 1/6.
    Error details: MapiExceptionCorruptData MapiExceptionCorruptData: Unable to set properties on object. (hr=0x8004011b, ec=-2147221221)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=64]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=300][latency=15]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropSetProps [10]
        Lid: 17082   ROP Error: 0x8004011B
        Lid: 30561  
        Lid: 21921   StoreEc: 0x8004011B
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropSetProps [10]
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x677E0102
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0xE9A0102
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0xE990102
        Lid: 4960    StoreEc: 0x8004011B
        Lid: 51683  
        Lid: 53731   StoreEc: 0x8004011B
        Lid: 58339   dwParam: 0x185D1
        Lid: 58851   StoreEc: 0x8004011B
        Lid: 5728    StoreEc: 0x8004011B
        Lid: 54592  
        Lid: 35136   StoreEc: 0x8004011B
        Lid: 51520  
        Lid: 3031    StoreEc: 0x8004011B
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x8004011B
        Lid: 25761  
        Lid: 1940    StoreEc: 0x8004011B
        Lid: 22561  
        Lid: 30753  

    After that error, the mailbox is not reachable anymore. The person get's an error in Outlook that Exchange is not reachable and in OWA she's got a message that her mailbox is being moved.

    Tuesday, October 01, 2013 3:33 PM

Answers

  • Hi,

    I have searched for the similar cases, and the error message turns out that this issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox. Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move process when you move many mailboxes at the same time.

    The recommended resolution is to restore the data from the backup to a new mailbox for the affected users, and proceed for mailbox migration upgrade the server to Exchange 2010 SP3.

    Hope it can help.

    Regards,

    Rebecca

    Wednesday, October 02, 2013 3:29 AM

All replies

  • How long did you wait? 

    My experience is that you can ignore this error.  You can adjust the number of retries if you want.  This is a lot worse going to Exchange 2013, where the retry count is 50, so it takes forever for moves to complete.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."


    Wednesday, October 02, 2013 12:35 AM
  • Hi,

    I have searched for the similar cases, and the error message turns out that this issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox. Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move process when you move many mailboxes at the same time.

    The recommended resolution is to restore the data from the backup to a new mailbox for the affected users, and proceed for mailbox migration upgrade the server to Exchange 2010 SP3.

    Hope it can help.

    Regards,

    Rebecca

    Wednesday, October 02, 2013 3:29 AM