Hybrid Configuration Wizard error: Validate Hybrid Agent for Exchange usage - Timeout

W.Othman 96 Reputation points
2021-08-12T21:47:34.537+00:00

I'm trying to configure Exchange hybrid, for the first time, to migrate from Office 2013 to O365. I'm getting the following error: Validate Hybrid Agent for Exchange usage - Timeout
I tried to find some more info in the log:

                                  TestMigrationServerAvailabilityOutcome {ErrorDetail='Microsoft.Exchange.Migration.MigrationServerConnectionFailedException: Die Verbindung mit Server 'xxx.resource.mailboxmigration.his.msappproxy.net' konnte nicht hergestellt werden. ---> Microsoft.Exchange.MailboxReplicationService.MRSRemoteTransientException: Fehler beim Aufruf von "https://xxx.resource.mailboxmigration.his.msappproxy.net/EWS/mrsproxy.svc", da kein Dienst am angegebenen Endpunkt gelauscht hat.    

Fehlerdetails: There was no endpoint listening at https://xxx.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 server returned an error: (400) Bad Request. ---> Microsoft .Exchange.MailboxReplicationService.MRSRemotePermanentException: There was no endpoint listening at https://xxx.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 server returned an error: (400) Bad Request.
--- End of inner exception stack trace ---

I tried to use Remote Connectivity Analyzer, the Inbound SMTP E-Mail test failed and showing the following error:

Attempting to send a test email message to sven.wenker@Beam .de using MX XX.mx.XX.net. Delivery of the test email message failed.
Additional Details
The server returned status code 550 - Mailbox unavailable. The server response was: 5.7.1 Fix reverse DNS for xxx.xxx.xxx.xxx
Ausnahmedetails:
Nachricht: Mailbox unavailable. The server response was: 5.7.1 Fix reverse DNS for xxx.xxx.xxx.xxx
Typ: System.Net.Mail.SmtpException
Stapelüberwachung:
at System.Net.Mail.MailCommand.CheckResponse(SmtpStatusCode statusCode, String response)
„at System.Net.Mail.MailCommand.Send(SmtpConnection conn, Byte[] command, MailAddress from, Boolean allowUnicode)
„at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, Boolean allowUnicode, SmtpFailedRecipientException& exception)
„at
System.Net.Mail.SmtpClient.Send(MailMessage message)
„at Microsoft.M365.RCA.ConnectivityTests.SmtpMessageTest.PerformTestReally()

Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,910 questions
0 comments No comments
{count} votes

Accepted answer
  1. W.Othman 96 Reputation points
    2021-08-19T12:30:34.397+00:00

    I somehow managed to get it working and could successfully run the wizard to the end. I had to update some PS Modules and suddenly after connecting to azure via PS have worked.
    Still, as it seems the Connectors weren't really set properly, I could see them, but they were not working. I have noticed this only after migrating the first mailbox and nothing worked after this.

    I had after this to contact Microsoft to solve this issue. They also couldn't say why it's not working with Modern Topology, therefore we had to switch to Classic Full to get it working.

    Outlook didn't connect seamlessly to Office 365 after migration and I had to set up email on the mobile phone again completely to get it working again.

    Microsoft Support has said there was an issue on the bach end of our Tenant and it has been solved now, so hopefully, migrating the next mailbox will be better :)


2 additional answers

Sort by: Most helpful
  1. KyleXu-MSFT 26,211 Reputation points
    2021-08-13T06:53:37.153+00:00

    @W.Othman

    Make sure your Exchange server is published to the Internet and MRSproxy is enabled on your Exchange server:

    Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $true   
    

    If it still failed, could you provide screenshot about which step this issue occur?


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. W.Othman 96 Reputation points
    2021-08-13T14:06:21.717+00:00

    I already tried this command and just to be sure I have trided it again but it didn't help :(
    Please find the screenshot below,
    123152-verbindung-mit-server.jpg