Warning during mailbox move on 2010

Posted on 2013-06-13
Last Modified: 2013-06-19
Never saw this before on Exchange 2010. Just moving empty mailboxes that where just created from one db to another. I am seeing a lot of these warnings in the application log. Move seems to go OK. In some case, the status says completed with warnings but the log show Request Completed Successfully.

Log Name:      Application
Source:        MSExchangeIS
Date:          6/13/2013 7:54:24 PM
Event ID:      9660
Task Category: Logons
Level:         Warning
Keywords:      Classic
User:          N/A

User Display Name(/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Display Name) failed to sign in because their mailbox is in the process of being moved.

I know for a fact that the user is NOT logged in or trying to login. It seems to happen with any mailbox. I did some checking on this and found it to be a common problem. It looks like it started with Exchange 2010 SP2 RU3 or 4 and apparently has carried into SP3. Another I noticed is that mailboxes now show up immediately in disconnected mailboxes after a move. I remember in the past, it took 24 hours or you had to do a clean-mailboxdatabase command against the database to get them to show up.

Using Exchange 2010 SP3 on Windows 2008 R2 SP1. Have two CAS servers and two MB servers in a two node DAG. Does anyone know if there is a fix for this. Apparently the move is none the worse but it takes longer to move a mailbox because it gets stuck at 99% complete and gets delayed when it tries to do it final cleanup.
Question by:shadowtuck
  • 4
LVL 12

Expert Comment

ID: 39247060

Could you please execute the following cmdlet in Exchange Management Shell  to see if there is any error available?

Get-mailboxstatistics -Identity <UserName> -IncludeMoveReport | select movehistory

Also, please increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service. This will help to collect more information regarding this event.

This error could be because the new mailbox information is not replicated. Please wait for 30 minutes after creating mailbox and then try initiating mailbox move. Also, please try sending a test mail to one of the mailbox and then try to move it and see if the error is coming.

Author Comment

ID: 39247283
Here is the output for one user. They are basically all the same for those that did get warnings. Not all mailboxes had the issue.

{(6/13/2013 7:58:20 PM: TargetMDB=MADB1, Size=6.111 KB (6,258 bytes), Duration=00:04:03, Warning=Warning: Failed to clean up the source ...

Like I said, I also noticed that the mailbox now shows up in disconnected mailboxes immediately after the move. This was different from the past when it took 24 hours or you had to run a clean-mailboxdatabase to get the mailbox to show up.

The next time I move a mailbox, I will increase the logging.

Author Comment

ID: 39247383
Hi. I did move a few mailboxes in my test environment and the logs in the EMC are below. I get this by going into the Move Request folder, select the mailbox and clicking the Log tab.

 Its the same for each MB. I did turn up logging on the MB Rpl Service but only the 9660 event is still showing up. The log below is for one particular mailbox. Its confusing because first it says cleanup was successful and then it says it failed. There is a 30 second delay between each retry and this greatly slows down mailbox moves. I am starting to think this is some kind of bug. In some cases, it just says Complete at the end and in other cases, it says completed with warnings.

6/14/2013 8:19:57 AM [Exchange01] Move has completed and final clean up has started.
6/14/2013 8:19:57 AM [Exchange01] Source mailbox 'Primary (a484d016-9ad6-4937-a91c-a4638b8cfcd4)' was successfully cleaned up after the move.
6/14/2013 8:19:57 AM [Exchange01 Target mailbox 'Primary (a484d016-9ad6-4937-a91c-a4638b8cfcd4)' was successfully reset after the move.
6/14/2013 8:19:57 AM [Exchange01] Post-move cleanup failed. The operation will try again in 30 seconds (1/6).
6/14/2013 8:20:27 AM [Exchange01] Post-move cleanup failed. The operation will try again in 30 seconds (2/6).
6/14/2013 8:20:57 AM [Exchange01] Post-move cleanup failed. The operation will try again in 30 seconds (3/6).
6/14/2013 8:21:28 AM [Exchange01] Post-move cleanup failed. The operation will try again in 30 seconds (4/6).
6/14/2013 8:21:58 AM [Exchange01] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
6/14/2013 8:22:29 AM [Exchange01] Request is complete.

Accepted Solution

shadowtuck earned 0 total points
ID: 39247504
Hello. Good news for anyone that has this issue. It is apparently fixed in Update Rollup 1 for SP3 per this article.

I will be installing it in our test environment and hopefully it will fix this problem.

Author Closing Comment

ID: 39258784
Found solution to own problem

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question