In our previous blog post we covered an overview of what migration endpoints are, how to find them and what makes them tick. In this post, we will cover related troubleshooting. Note that this post h...
Updated Mar 30, 2020
Version 5.0
Blog Post
We are using Exchange Hybrid Agent and when we run the Wizard it fails with the below error and I ran the Test-migrationserveravailability command from EoL PowerShell and it brought back the same error.
Any help to fix this error is appreciated.
PS C:\Users\murali> Test-MigrationServerAvailability -ExchangeRemoteMove -RemoteServer GUID.resource.mailboxmigration.his.msappproxy.net -Credentials(get-credential)
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
Supply values for the following parameters:
Credential
RunspaceId : ID
Result : Failed
Message : The connection to the server 'GUID.resource.mailboxmigration.his.msappproxy.net' could not be completed.
SupportsCutover : False
ErrorDetail : Microsoft.Exchange.Migration.MigrationServerConnectionFailedException: The connection to the server
'GUID.resource.mailboxmigration.his.msappproxy.net' could not be completed. --->
Microsoft.Exchange.MailboxReplicationService.MRSRemoteTransientException: The call to
'https://GUID.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc' failed because no service was listening on the specified
endpoint. Error details: There was no endpoint listening at https://GUID.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc
that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. --> The remote name could
not be resolved: 'GUID.resource.mailboxmigration.his.msappproxy.net' --->
Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: There was no endpoint listening at
https://GUID.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc that could accept the message. This is often caused by an
incorrect address or SOAP action. See InnerException, if present, for more details. ---> Microsoft.Exchange.MailboxReplicationService.MRSRemotePermanentException: The
remote name could not be resolved: 'GUID.resource.mailboxmigration.his.msappproxy.net'
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceFault.<>c__DisplayClass106_0.<ReconstructAndThrow>b__0()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(Action operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceFault.ReconstructAndThrow(String serverName, 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)
at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.CallService(Action serviceCall, String context)
at Microsoft.Exchange.MailboxReplicationService.WcfClientWithVersion`2.CallService(Action serviceCall, String context)
at Microsoft.Exchange.Migration.MigrationExchangeProxyRpcClient.CanConnectToMrsProxy(Fqdn serverName, Guid mbxGuid, NetworkCredential credentials, LocalizedException&
error)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Migration.DataAccessLayer.ExchangeRemoteMoveEndpoint.VerifyConnectivity()
at Microsoft.Exchange.Management.Migration.MigrationService.Endpoint.TestMigrationServerAvailability.InternalProcessEndpoint(Boolean fromAutoDiscover)
TestedEndpoint :
IsValid : True
Identity :
ObjectState : New