Not able to move Mailbox from one Database to another Database

Came across an issue that when you try to move few mailboxes from one Database to another database, It is given an error

Error details: MapiExceptionNoAccess: Unable to query table rows. (hr=0x80070005, ec=-2147024891)

It happened with Exchange 2010 SP3 RU8 and even it reoccurred post upgrading Exchange SP3 RU9

1

2

Error Message:

Couldn’t switch the mailbox into Sync Source mode.

This could be because of one of the following reasons:

  Another administrator is currently moving the mailbox.

  The mailbox is locked.

  The Microsoft Exchange Mailbox Replication service (MRS) doesn’t have the correct permissions.

  Network errors are preventing MRS from cleanly closing its session with the Mailbox server. If this is the case, MRS may continue to encounter this error for up to 2 hours – this duration is controlled by the TCP KeepAlive settings on the Mailbox server.

Wait for the mailbox to be released before attempting to move this mailbox again.

 

MapiExceptionMailboxInTransit: Unable to open message store. (hr=0x80004005, ec=1292)

Diagnostic context:

    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=189]

    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=256][latency=1]

    Lid: 23226   — ROP Parse Start —

    Lid: 27962   ROP: ropLogon [254]

    Lid: 17082   ROP Error: 0x50C    

    Lid: 26937 

    Lid: 21921   StoreEc: 0x50C    

    Lid: 27962   ROP: ropExtendedError [250]

    Lid: 1494    —- Remote Context Beg —-

    Lid: 26426   ROP: ropLogon [254]

As per the support Article, You need Upgrade to Exchange 2010 SP3 Roll-Up 10 to resolve this issue. If you still looking for temporary solution for the below versions(>RU10), you can go for exporting the mails to PST and recreate the mailboxes in another database where you planned to move them.

One thought on “Not able to move Mailbox from one Database to another Database”

Leave a Reply to gnanavetrivel Cancel reply

Your email address will not be published. Required fields are marked *