ExchangePro: Exchange 2010 to office 365 Failed to create new move request (4312122)

Issue

We recently ran into an issue with a customer that was preventing us from migrating Exchange 2010 users to Office 365. 

This was the error we were seeing:

Log Name:      Application

Source:        BTE2EMCP

Date:          7/11/2013 10:08:03 AM

Event ID:      0

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      TIS-BTE2EDEV.ad.contoso.com

Description:

E2E MCP (Submit Pending Jobs)

Failed to create new move request for user bbrinza@contoso.com<mailto:bbrinza@contoso.com>.

PowerShell Host: pod51019psh.outlook.com

PowerShell Pipeline: 

New-MoveRequest -Identity "bbrinza@contoso.com <mailto:bbrinza@contoso.com >" -TargetDeliveryDomain "x.dev.sfgov.org" -RemoteCredential (Get-Credential "ad\admnalim") -RemoteGlobalCatalog "ALL-VW-ADDC003.AD.contoso.com " -Remote:$True -RemoteHostName "x.dev.contoso.com "

Pipeline Errors:

The call to 'https://x.dev.contoso.com/EWS/mrsproxy.svc' failed. Error details: The remote server returned an unexpected response: (405) Method Not Allowed. --> The remote server returned an error: (405) Method Not Allowed. 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="BTE2EMCP" />

    <EventID Qualifiers="0">0</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-07-11T17:08:03.000000000Z" />

    <EventRecordID>4789</EventRecordID>

    <Channel>Application</Channel>

    <Computer>TIS-BTE2EDEV.ad.contoso.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>E2E MCP (Submit Pending Jobs)

Failed to create new move request for user bbrinza@contoso.com<mailto:bbrinza@not.contoso.com>.

PowerShell Host: pod51019psh.outlook.com

PowerShell Pipeline:

New-MoveRequest -Identity "bbrinza@contoso.com<mailto:bbrinza@contoso.com>" -TargetDeliveryDomain "x.dev.contoso.com" -RemoteCredential (Get-Credential "ad\admnalim") -RemoteGlobalCatalog "ALL-VW-ADDC003.AD.contoso.com" -Remote:$True -RemoteHostName "x.dev.contoso.com"

Pipeline Errors:

The call to 'https://x.dev.contoso.com/EWS/mrsproxy.svc' failed. Error details: The remote server returned an unexpected response: (405) Method Not Allowed. --&gt; The remote server returned an error: (405) Method Not Allowed..

</Data>

  </EventData>

</Event> 

Cause

When trying to resolve the issue we noticed that there was a handler mapping missing from the EWS website on the Exchange server. To re-add this handler and resolve the issues complete the following steps:

Solution

1. On the Exchange server, open IIS Manager, and navigate to the EWS Website
2. Select Handler Mappings
3. If the Handler Mapping titled svc-Integrated is not listed select Add Managed Handler in the top right corner
4. For the request path: enter *.svc
5. For the type: enter System.ServiceModel.Activation.HttpHandler, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
6. For the Name: enter svc-Integrated

         [cid:image001.png@01CE7E4B.BC67F6A0]

7. Then click OK
8. Then complete an IISReset

To verify that this is now working, you can open your browser and navigate to https://exchangeservername.com/EWS/mrsproxy.svc . You should see an XML response from your server and not a 404 or 405 error message.