Mailbox ‘xyz’ has a completed move request associated with it

Share this:

That is a simple error but sometimes it shows up in our Community Forums,  basically we cannot move a mailbox if  we have any previous move request associated to that given mailbox, even though if that move request has the status Completed.

As a best practice, we should always try to clean up the Move Request after completing it. If you don’t want to do that, you  could try to clean them up in a time basis.

In this post we tried first to move the Discovery Mailbox between two Exchange Servers and as soon as we run the New-MoveRequest cmdlet we are getting the message below.

image

The solution is simple, just make sure that you clean up the Move Requests, first step is to list such requests..

image

If they are all completed, you don’t have to worry, just run the following cmdlet to clear up the list. If you don’t have them complete, check their status and proceed from there (wait to complete or if it is failed we can check the logs to fix the issue).

image

Finally, we can go back to the cmdlet that generated the topic of this post and now you move request should be performed just fine.

image

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at ITPROCentral.com, MSExchange.org, Techgenix.com and Anderson Patricio.org (Portuguese).

Related Post

Error creating a DAG without AAP in Exchange Serve... In this post we are going over the error “Some or all identity references could not be translated” or “A server-side administrative operation has fail...
Fixing the error “The network path was not found” ... In situations where a new server is built to be used as witness server the administrator can get the error “The network path was not found” during the...
Managing DAG in Exchange Server 2013 – The Series... In this series we are going over the entire process to create a DAG environment in Exchange Server 2013. At the end of the series we will have built ...
Managing DAG: Adding nodes and DAC mode In this Tutorial of our Managing DAG in Exchange Server 2013 series we will be adding additional nodes to our newly created DAG and also configuring i...