Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3677
  • Last Modified:

Warning during mailbox move on 2010

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
Computer:      Exchangeserver1.domain.com

Description:
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.
0
shadowtuck
Asked:
shadowtuck
  • 4
1 Solution
 
SreRajCommented:
Hi,

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.
0
 
shadowtuckAuthor Commented:
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.
0
 
shadowtuckAuthor Commented:
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.
0
 
shadowtuckAuthor Commented:
Hello. Good news for anyone that has this issue. It is apparently fixed in Update Rollup 1 for SP3 per this article.

http://support.microsoft.com/kb/2763065


I will be installing it in our test environment and hopefully it will fix this problem.
0
 
shadowtuckAuthor Commented:
Found solution to own problem
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.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now