Error after New Remote Move Request

Asked By 30 points N/A Posted on -

Hello there!

I have attached an image with full text details showing an error dialog box. I got this error after trying to do a new remote move request. The error message came up for about a few seconds after successfully completing the remote mailbox move. There’s no problem in moving the mailbox however, I am just confused why I got that error message? Do you have any idea what causes the error? Any help from you guys are greatly appreciated.

Could not load type 'Microsoft.Exchange.MailboxReplicationService.RequestPriority' from assembly 'Microsoft.Exchange.MailboxReplicationService.Common, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Microsoft Exchange Critical Error

Could not load type
'Microsoft.Exchange.MailboxReplicationService.RequestPriority' from assembly
'Microsoft.Exchange.MailboxReplicationService.Common, Version=,
Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Best Answer by tibor.tokie
Best Answer
Best Answer
Answered By 0 points N/A #92148

Error after New Remote Move Request


Dear Rochelle Cruz,

Prior to Microsoft support page, the update rollup 5 for Exchange Server 2010 Service Pack 1 solves the error message that you have encountered. Please follow this link in order to get the rollup update to our machine: 

Also, you need to check the version of the Exchange server with the Replication service version; they both should be of the same version. Another reason for this error might be that the staged migrations are not supported by the Exchange server. You might try to use EXO 2010 migration server by a hybrid deployment (Rich coexistence).

Hope this may help you.

Best of luck.

Answered By 0 points N/A #197972

Error after New Remote Move Request


I would like to ask you if you have done any Rollups installations. If you have you should do patch to your server. Moreover, if you have installed ''Windows Management Framework 3.0'', this could be problem either. You should uninstall all these program and check if the problem remains. If it is not solved check the Microsoft support.

Login/Register to Answer

Related Questions