Mailbox Movement Error

We are migrating mailbox from one database to another in Exchange 2010 but is stuck & getting below error.

11/30/2013 9:21:18 PM [MS06] The job encountered too many transient failures (60) and is quitting.
11/30/2013 9:21:18 PM [MS06] Fatal error SourceMailboxAlreadyBeingMovedTransientException has occurred.
Error details: 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)
Who is Participating?
RadweldConnect With a Mentor Commented:
From the Management Shell, does Get-MoveRequest return the failed move? it should do and should also list that it's failed.

You can then run Remove-MoveRequest -Identity (display name) to clear the move request that's preventing you from re-running the job. it's worth just re-running the move just to see if it will work however this time however you might want to perform the move using PowerShell and set some additional switches,

-BadItemLimit (numerical value) and -AcceptLargeDataLoss if the baditem limit is greater than 50.
Is the mailbox is already in the moving process.
Please check if the mailbox move request is already running.
sanjayambreAuthor Commented:
Checked that no mailbox movement is in process from any exchange server.
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.

sanjayambreAuthor Commented:
Is there any alternate solution to resolved this issue..
Could you check the attribute of the mailbox, look for this attributes if they are available:


if yes, mean other administrator is moving the mailbox since If these attributes are not removed then another New-MoveRequest cannot be issued for the same mailbox.
sanjayambreAuthor Commented:
These attributes are available but values are not set.
sanjayambreAuthor Commented:
I think my questions is being misunderstood.....there is no issue with starting or removing move request.

while starting new move request (by removing previous one)  for the particular mailbox, its works upto 10 % & then get stucked with fatal error which has already been shared.

Issue with one mailbox only , others are moved smoothly.
Do you try move the mailbox using Exchange Management Shell with specified -badlimit

as suggested by Radweld
I would read this blog, you will need to locate the log file for the failed move and examine it, post the results here.
sanjayambreAuthor Commented:
Yes, we tried to move using exchange management shell by specifying -badlimits but result is the same.
sanjayambreAuthor Commented:
Just closing the case
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.