Exchange Local Move requests stuck at Queued

I've recently upgraded to Exchange 2010 SP3.  I can't seem to move users to different databases anymore, instead they stay stuck at queued.

This happens with mailboxes that haven't ever been moved before (this is not the soft-deleted or adsi move flags/source etc attribute issue)

I tried rebooting all mail servers, restarting mailbox replication service on cas, deleting the move requests.  Nothing seems to work.
billFmurrayAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
SeanConnect With a Mentor System EngineerCommented:
are the databases healthy?

 You can open the command shell and run a few commands to check the status of the move request.

Get-MoveRequest

Get-MoveRequestStatistics

Get-MailboxStatistics

also check these two sites to see if it is related:
http://www.windowsinfo.eu/?p=347
http://www.sysadminsblog.com/microsoft/event-2937-homemta-pointing-to-the-deleted-objects-container/
0
 
billFmurrayAuthor Commented:
It turned out to just take forever but eventually moved.  Not sure why though.

I had tried all those steps.  Everything just said queued or moving.  DB's were in good state.  I don't think that last article applies because even newly created objects would get stuck.  

Took about 4 hours for it to start.  Must be something in Exchange/AD replication I guess.

Thanks for your input though.  Giving you the points.
0
 
billFmurrayAuthor Commented:
*before SP3, it would only take a few minutes to initialize move
0
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.