Article ID: 2702674 - View products that this article applies to.
In the Microsoft Office 365 and an on-premises Microsoft Exchange Server environment are hybrid deployment Microsoft Exchange Online. Displays the following error message when using the Exchange Management Console or Windows PowerShell to Office 365 environmental move the mailboxes from the on-premise environment.
Entries such as the following appears in the on-premise Exchange 2010 coexistence Server Internet Information Services (IIS) logs.
The call to https://webmail.contoso.com/ews/mrsproxy.svc failed because no service was listening on the specified endpoint. Error details: There was no endpoint listening at https://webmail.contoso.com/ews/mrsproxy.svc that could accept the message. This is often caused by an incorrect address:
(404) Not Found. (Reference: specify the endpoint in the service to 呼出semasenn Https://webmail.contoso.com/ews/mrsproxy.svc. Error details: https://webmail.contoso.com/ews/mrsproxy.svc to approve the message endpoint. Occurs if you do not type the correct address. : (404) Not Found)
2011-10-25 22: 40: 46 192.168.200.33 POST /EWS/mrsproxy.svc-80-192.168.200.1-401 1 2148074254 93
2011-10-25 22: 40: 46 192.168.200.33 POST /EWS/mrsproxy.svc-80 CONTOSO \jsmith 192.168.200.1-404 0 0 62
Before you move mailboxes, use remote mailbox move request Wizard in the Exchange Management Console to create a move request, and at the end of the wizard and are prompted for credentials. Prompt for credentials is not included in the wizard. Displayed in a separate window.
You may issue rules to use Microsoft Forefront Threat Management Gateway (TMG) and the port is not configured correctly. And without need of prior authentication requests are not redirected to port 80, so requires creation of additional rules in Forefront TMG.
If you have reverse proxy (example: Forefront TMG or Microsoft Internet Security, and Security and Acceleration (ISA) Server) and configure the Exchange services in a perimeter network and require pre-authentication, if Exchange Mailbox Replication Proxy (MRSProxy) service does not function properly.
To resolve the problem, create a additional rules in Forefront TMG or ISA Server. Create a source Exchange 2010 rules (admit authenticated traffic prior to the internal Exchange Server) is applied, any new rules applicable to. The following criteria is required to rule.
How to configure Forefront TMG to deploy the hybrid between Office 365 and an on-premises Exchange Server Exchange Online, see the following Office 365 community Web site.
How to configure TMG for Office 365 (Exchange) hybrid deploymentHybrid reverse proxy configuration details, see Office 365 deployment guide configuring the hybrid reverse proxy section. This guide is available from the following Microsoft Web site.
http://www.Microsoft.com/downloads/ja-JP/details.aspx?FamilyId=5ace498b-4b8d-4853-99c0-710f6130c217See how to configure Forefront TMG 2010 to Exchange Server 2010 at the following Microsoft Web site is "Publishing Exchange Server 2010 with Forefront UAG and TMG' (in the Exchange Server 2010 configuring Forefront UAG and TMG).
http://www.Microsoft.com/download/en/details.aspx?displaylang=en&ID=8946If you need additional information Office 365 community
(http://community.office365.com/ja-jp/default.aspx)Please see the Web site.
Article ID: 2702674 - Last Review: October 13, 2014 - Revision: 10.0