How to complete a migration batch with PowerShell in Exchange Online manually? You created new…
We are installing the Hybrid Configuration Wizard (HCW) on the Exchange Server, but an error shows up. The error is HCW8078 – Migration Endpoint could not be created. Why is it happening, and what is the solution?
Table of contents
Hybrid Configuration Wizard
We like to move mailboxes to Exchange Online from Exchange on-premises. But, before doing that, we have to download and install the Office 365 Hybrid Configuration Wizard.
By establishing a hybrid deployment, you can extend the feature-rich experience and administrative control you have with your existing on-premises Exchange Server organization to the cloud. A hybrid deployment also offers support for a cloud-based archiving solution for your on-premises mailboxes with Exchange Online Archiving. It may also serve as an intermediate step towards a complete migration of your on-premises mailboxes to Exchange Online.
HCW8078 – Migration Endpoint could not be created
In the Hybrid Configuration Wizard, we can select two options in the Hybrid Topology:
- Exchange Classic Hybrid Topology
- Exchange Modern Hybrid Topology
Exchange Modern Hybrid Topology
In the setup wizard, we selected the option Use Exchange Modern Hybrid Topology.
The HCW installs the Hybrid Agent. There are four primary phases:
- Download the agent install package.
- Installation of the agent on the local computer (note: this prompts for your Microsoft 365 or Office 365 Global Administrator credentials again).
- Registration of the agent in Azure, including creation of the URL used to proxy requests. The URL has the format: uniqueGUID.resource.mailboxmigration.his.msappproxy.net.
- Testing migration viability from your Microsoft 365 or Office 365 organization to your on-premises Exchange organization via the agent.
Only this time, an error shows up.
Let’s rerun HCW, this time selecting Classic Hybrid Topology.
Exchange Classic Hybrid Topology
Click on the back button or close the Office 365 Hybrid Configuration setup. Start the wizard, and this time we will select Use Exchange Classic Hybrid Topology.
An error didn’t show up, that’s because it didn’t need to download, install, register, and test the Hybrid Agent. The wizard will give a couple more steps to configure. After proceeding with the steps, the following error shows up at the final stage.
Note: Press F12 in the Office 365 Hybrid Configuration Wizard to open the Diagnostic Tools. It gives you a quick way to open the log file and many more options.
The full details are below.
Your Exchange Hybrid Configuration has completed but a few items need to addressed or potentially configured manually. Please see the details below. Configure MRS Proxy Settings HCW8078 Migration Endpoint could not be created. Microsoft.Exchange.Net.EndpointNotFoundTransientException The call to 'net.tcp://am6pr08mb4104.eurprd08.prod.outlook.com/Microsoft.Exchange.MailboxReplicationService' failed because no service was listening on the specified endpoint. Error details: There was no endpoint listening at net.tcp://am6pr08mb4104.eurprd08.prod.outlook.com/Microsoft.Exchange.MailboxReplicationService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. System.ServiceModel.EndpointNotFoundException There was no endpoint listening at net.tcp://am6pr08mb4104.eurprd08.prod.outlook.com/Microsoft.Exchange.MailboxReplicationService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object ins, Object outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at : at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Exchange.MailboxReplicationService.IMailboxReplicationService.ExchangeVersionInformation(VersionInformation clientVersion, VersionInformation& serverVersion) at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.<>c__DisplayClass4_0.<CallService>b__0() at Microsoft.Exchange.Net.WcfClientBase`1.CallService(Action serviceCall, String context)
Solution for HCW8078 – Migration Endpoint could not be created
After looking in the logs, it became clear that the problem is not on our end but at Microsoft. After talking with Microsoft and telling them that the issue lies at their side, they first tried to restart the Office 365 tenant services. That didn’t help. Microsoft created a ticket, and they had to investigate further.
After a couple of hours, they reached out to me and told me that there is an issue at Microsoft end. It became a priority problem because more tenants are starting to have problems setting up the Hybrid Configuration Wizard. It took Microsoft about 24 hours to completely fix the problem.
After that, we did rerun the Hybrid Configuration Wizard. This time it was a success!
Keep reading: Hybrid Configuration Wizard fails to connect »
In this article, you learned why you get HCW8078 – Migration Endpoint could not be created. Looking in the Hybrid Configuration Wizard logs clearly showed that the problem is on Microsoft side. The solution to this problem is to contact Microsoft. After their investigation, the problem was identified and later on fixed.
Did you enjoy this article? You may also like Find RemoteHostName URL for mailbox migration. Don’t forget to follow us and share this article.