![microsoft dynamics rms hqevent log too large microsoft dynamics rms hqevent log too large](https://i1.rgstatic.net/ii/profile.image/935765806678016-1600115362218_Q64/Teja-Parker.jpg)
Wait for the mailbox to be released before attempting to move this mailbox again. If this is the case, MRS may continue to encounter this error for up to 2 hours – this duration is controlled by the TCP KeepAlive settings on the Mailbox server. Network errors are preventing MRS from cleanly closing its session with the Mailbox server. The Microsoft Exchange Mailbox Replication service (MRS) doesn’t have the correct permissions. This could be because of one of the following reasons:Īnother administrator is currently moving the mailbox. Message : Error: Couldn’t switch the mailbox into Sync Source mode. The error I get in the MailboxStatistics report (see above for cmdlet) reads: If I can lock the mailbox for longer, moves don’t timeout and fail is the theory behind why this happens I think MRS checks the registry key to see the KeepAliveTime and sets this to the lock time on the mailbox during the move. I am NOT restarting Windows, and so I am not changing the KeepAliveTime for the entire network stack. Now I need to be clear here – all I am doing is changing the registry key for this setting and restarting the MRS service on the source Exchange Server. I have found that by increasing TCP KeepAliveTime (contrary to all the advise online) that this solves the issue. When target Exchange tries to connect again, the source has lost the TCP port and so a new move is started, but the mailbox is still locked for the old move. What can happen is the move is progressing and a check happens for changes to the source mailbox – this takes a long time to complete and something times out. If you get the following then the mailbox is probably too large for a successful move, which means the source server or network has not got the resources. Search the report that you have saved in the above cmdlet and search for “Error” in the text file.
Get-MoveRequestStatistics "View the Move Request Statistics log for one of your failed mailbox moves: Get-MoveRequest -MoveStatus failed | Get-MoveRequestStatistics | fl badite* Here is why:įirst make sure no bad items in your failed moves – this is not a fix for bad items, this is a fix where things timeout: This is the opposite – increase the value and do not reboot the server. Often you will see to reduce the TCP KeepAliveTime and reboot the server. The fix for this is counter though to everything else you read online about this. A large mailbox (or mailbox and archive) wont move to the target because the process of checking what the changes are in the mailbox take too long, the network or Exchange Server times out the users move and then reports the mailbox is locked. I have seen this situation a number of times.