Article ID: 2669562 - View products that this article applies to.
You have a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and your on-premises Microsoft Exchange Server environment. When you try to move mailboxes to or from Office 365, you receive the following error message:
You were previously able to successfully move mailboxes to or from Office 365 and your on-premises Exchange Server environment. You experience this symptom only after you upgrade the on-premises environment from Exchange Server 2010 Service Pack 1 (SP1) to Exchange Server 2010 Service Pack 2 (SP2).
Exception has been thrown by the target of an invocation.
This issue occurs if the Web.config file was overwritten during the upgrade from Exchange Server 2010 Service SP1 to Exchange Server 2010 SP2. Remote mailbox moves requires the Mailbox Replication Proxy (MRSProxy) service endpoint to be enabled on the Client Access server. In Exchange Server 2010 and in Exchange Server 2010 SP1, the MRSProxy setting is configured in the Web.config file.
In Exchange Server 2010 SP2, the MRSProxy settings are stored in Active Directory and are configured by using the Set-WebServicesVirtualDirectory Windows PowerShell cmdlet.
Note There are several possible causes of this error message. This article discusses one scenario that may cause this error message.
Use the Set-WebServicesVirtualDirectory cmdlet to re-enable MRSProxy on every Client Access server in the on-premises environment through which you want to let remote move requests pass. To do this, follow these steps:
For more information about this issue, visit the following Microsoft website:
http://community.office365.com/en-us/w/exchange/remote-mailbox-moves-fail-after-installing-exchange-2010-sp2.aspxFor more information about how to troubleshoot the error message that is mentioned in the "Symptoms" section, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2626696/ )"Exception has been thrown by the target" error in a hybrid deployment of Office 365 and your on-premises environment
Still need help? Go to the Office 365 Community
Article ID: 2669562 - Last Review: July 9, 2014 - Revision: 13.0