Hybrid mailbox move throws error "Exception has been thrown by the target of an invocation."

We have seen a few cases recently that throw the error depicted below when trying to on-board or Off-board a mailbox to and from Office 365. This only occurs when in a hybrid deployment and only in certain circumstances.

 

additional autodiscover issue

There is also a secondary problem that can also occur when creating the Organization Relationship from the cloud based organization. The error you may encounter here is related to the creation of the Organization Relationship when the autodiscover option is used for creating the relationship.

"Federation Information could not be received from the external organization"

 

In both cases, you can investigate the on-premises Exchange 2010 sp1 coexistence server IIS logs. You can find them in the C:\Inetpub\logs directory. You will see a 405 error in the log for the connection to the respective endpoint.

  • The Mailbox move endpoint would be MRSProxy.svc
  • The Autodiscover endpoint is Autodiscover.svc

If you search the above mentioned IIS log for the endpoints specified and see a 405 error at the end of the line you will know that the "method is not allowed".

The error in the IIS log will look similar to the following:

 9/22/2011 11:24 PM:32 10.10.10.1 POST /EWS/mrsproxy.svc - 443 test\admin 10.10.10.12 - 405 0 1 15

You may also notice that other connections to the CAS, such as normal autodiscover for profile creation is not effected. This is because that does not use the "svc" endpoint. Any connection that use the svc endpoint will fail other endpoints will more than likely not be effected.

Cause

The cause of the issue is related to a missing handler mapping in the IIS configuration. The following image depicts the Handler Mapping location and which handler mapping to look for. You will notice that there is a handler mapping for "SVC-Integrated". If that is missing you should move on to the resolution section of this wiki to see how to address this issue.

 

Please take a backup of your IIS configuration ahead of time. The resolution should not cause any issues but a backup is always good to take before making any configuration changes.

At this point, I am not aware of why the handler mappings go missing. I will update this wiki when I find the cause of the missing handler mappings.

 

Resolution

Open a command prompt on the Exchange 2010 sp1 coexistence server and change to the " C:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation\" directory.

Then run " ServiceModelReg.exe –r"

This will reinstall all of the handler mappings into IIS, I did a restart of IIS afterwards but his may not be required.

Timothy Heeney (MSFT)