Hi francoisdek, It looks like a known issue in Exchange 2010 SP2. It will be resolved in Exchange 2010 SP2 RU5. Before that, to work around, you can try to uninstall Exchange 2010 SP2 RU4-v2 from all your Exchange servers. Thanks, Da Xu

Hi francoisdek, How are things going? We appreciate an update on the status of the issue. Thanks, Da Xu

I have Microsoft Exchange 2010 Version: 14.02.0318.004 (RU4v2) On all three of my CAS Servers the replication Service keeps on restarting. This causes Local Move Requests to complete with errors, and does not do a clean up at the end of the move. It delays moves, an causes frustration. Here is the move that completed with errors. Failed to clean up the source mailbox 'Primary (22cec362-b465-44f7-846a-xxxxxxxxx)' after the move. Attempt 3/6. Error details: MapiExceptionUnexpectedMailboxState MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634) at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException) at Microsoft.Mapi.ExRpcAdmin.DeletePrivateMailbox(Guid guidMdb, Guid guidMailbox, Int32 flags) at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.DeleteMailboxInternal(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass2a.<Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox>b__29() at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation) at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.DeleteMailbox(Int32 flags) at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass6d.<PostMoveCleanupSourceMailbox>b__6b() at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)

Its a known issue on moving mailbox, but we have to check if the service itself crashes constantly. Navigate to <Exchange Installation Path>\Program Files\Microsoft\Exchange Server\V14\Bin. Open the MSExchangeMailboxReplication.exe.config file using a text editor such as Notepad.Navigate to the MRSConfiguration section. You can edit the following properties: MaxCleanupRetries This property specifies the number of times that MRS should attempt to clean up a task. If the maximum number of attempts is reached, the task fails. You can specify a value from 0 through 100. The default value is 5. Change the value to 1 , So that it doesn't retry much times. http://technet.microsoft.com/en-us/library/ff963524.aspx if you want to cleanup the source mailbox To check the soft deleted ones Get-MailboxStatistics -Database "dbname" | Where { $_.DisconnectReason -eq "SoftDeleted" } | fl disp*,Mailbox* to remove the soft deleted ones. Remove-StoreMailbox Database "dbname" Identity "guid" MailboxState SoftdeletedSatheshwaran Manoharan | Exchange 2003/2007/2010/2013 | Blog:http://www.careexchange.in | Please mark it as an answer if it really helps you ------------- I do not represent the organisation I work for, all the opinions expressed here are my own. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Will try this setting on all three of the CAS Servers. The other frustration is that I use to move between 1500 to 2500 mailboxes per day - now only 20 if I am lucky. Is this because of this service restarting itself on all the servers? The first 20000 users moved within a week, now I am struggling to have people moved over. Ran the PSH command to check MRSHealth and found nothing wrong, but there is always one servers service not running, each time a different server. I seriously need to get a fix for this. I am moving mailboxes from one DAG to another in Exchange 2010.