Sign up for Office 365
Learn more about Office 365
When you are performing a cross forest mailbox move, this includes moving to and from Office 365, you may run into the following issue. This is assuming that you have upgraded to sp2 for Exchange 2010 and you had remote mailbox moves previously working.
The error message you will get is "Exception has been thrown by the target of an invocation.":
This is a very common error message and could mean many different things. This article simply explains one of the possible causes for this error.
The remote mailbox moves requires that the Client Access Server have the MRSProxy endpoint enabled. This was done in the EWS Web.Config file in Exchange 2010 RTM and sp1. The issues with the setting being in the Web.Config file is that every time you upgraded the Exchange server you ran the risk of that Web.Config file being overwritten.
In Exchange 2010 SP2, the settings for the MRSProxy have been moved to the Set-WebServicesVirtualDirectory and are now stored in Active Directory. The good news is that now the settings will live through service packs and rollups. The bad news is that the upgrade from Exchange 2010 SP1 to SP2 caused the settings to be removed. You will now have to run the following cmdlet to re-enable the MRSProxy on all of the upgraded Client Access Servers one last time.
The solution is to run the Set-WebServiceVirtualDirectory to enable the MRSProxy with the following cmdlet. You will need to do this for every Client Access Server that you want to allow the remote move requests to pass through. Before following the below mentioned steps you should run the Get-WebServicesVirtualDirectory cmdlet to ensure that the MRSProxyEnabled parameter is in fact set to False.
The new Hybrid Configuration Wizard that is introduced for Exchange 2010 sp2 for Office 365 coexistence will take care of the above mentioned action for you.
The solution is to run the Set-WebServiceVirtualDirectory to enable the MRSProxy with the following cmdlet. You will need to do this for every Client Access Server that you want to allow the remote move requests to pass through.
-Timothy Heeney (MSFT)
Already ran the reinstall referenced in another article, running this tells me that "server\ews(default Web site)" cannot be found on my dc.
"server\ews(default Web site)" it's incorrect, try "server\ews (default Web site)"