I am in the process of moving mailboxes from Exchange 2010 to 2013 (same forest) and keep running into a problems when trying to move multiple mailboxes.
I create the new move request, the first mailbox completes and then the rest sit in Queued status. I've had a look through the Application event logs and have a few errors.
The first:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '86fc9cf0-3f44-4b8f-8917-ee62a1543cdd'
Database GUID: '4e72ee67-4bf8-4fc1-910c-9ff88e1e9e9a'
Error: Resource reservation failed for 'MRS(RC-EX2013-01)' (Processor): load ratio 1.17142857142857, load state 'Overloaded', metric 82..
The second:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '86fc9cf0-3f44-4b8f-8917-ee62a1543cdd'
Database GUID: '4e72ee67-4bf8-4fc1-910c-9ff88e1e9e9a'
Error: Resource reservation failed for 'MdbWrite(Directors Mailbox Database)' (MdbLatency(Directors Mailbox Database)): load ratio -1, load state 'Unknown', metric (null)..
The third:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '5600e854-9e41-4b96-905d-320d4909d384'
Database GUID: '699ffe9a-6806-4663-ad9a-169a3eccc489'
Error: Resource reservation failed for 'MdbWrite(Archive Database 2013)' (CiAgeOfLastNotification(Archive Database 2013)): load ratio -1, load state 'Unknown', metric (null)..
Restarting the Microsoft Exchange Mailbox Replication service seemed to get it going again, but why do they occur in the first place?
These mailboxes are small (only a couple of hundred kb in size). I have another 250 odd to do ranging from a few hundred MB up to a couple of GB in size and don't want to run into any unexpected problems where requests just sit queued.
Does anybody have any ideas?