HCW8057 error message

I'm trying to migrate my exchange 2010 on premisis environment to Office 365 via the hybrid method. I have already synchronized my AD with azure. when I start the hybrid configuration wizard I get the following message HCW8057 at the end (see the picture).

Ive used the following commands to configure autodiscover:

Get-ClientAccessServer | Set-ClientAccessServer –AutoDiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

Get-ClientAccessServer | Select AutoDiscoverServiceInternalUri, AutoDiscoverSiteScope


Get-ClientAccessServer | ? {$_.AutoDiscoverSiteScope –eq “AD Site Name” } | Set-ClientAccessServer –AutoDiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml


Get-ClientAccessServer | Select AutoDiscoverServiceInternalUri, AutoDiscoverSiteScope

Get-ClientAccessServer | ? {$_.AutoDiscoverSiteScope –eq “AD Site Name” } | Set-ClientAccessServer –AutoDiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

Get-ClientAccessServer | Select AutoDiscoverServiceInternalUri, AutoDiscoverSiteScope

Set-ClientAccessServer -Identity DC-server -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml

Set-WebServicesVirtualDirectory -Identity "DC-server\EWS (default web site)" -InternalUrl https://mail.contoso.com/ews/exchange.asmx

Set-WebServicesVirtualDirectory -Identity "DC-server\EWS (Default web site)" -ExternalUrl https://mail.contoso.com/ews/exchange.asmx

Set-OABVirtualDirectory -Identity "DC-server\oab (default web site)" -InternalUrl https://mail.contoso.com/oab

Set-OABVirtualDirectory -Identity "DC-server\oab (default web site)" -ExternalUrl https://mail.contoso.com/oab


Get-OabVirtualDirectory | Set-OabVirtualDirectory –ExternalURL https://mail.contoso.com/oab

Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory –ExternalURL https://mail.contoso.com/ews/exchange.asmx

Set-OutlookAnywhere -Identity "DC-server\Rpc (Default Web Site)" -SSLOffloading $true -ClientAuthenticationMethod NTLM -IISAuthenticationMethods Basic,NTLM

Set-OutlookProvider -Identity EXCH -CertPrincipalName msstd:mail.contoso.com
Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:mail.contoso.com
Set-OutlookProviderF -Identity WEB -CertPrincipalName msstd:mail.contoso.com
Set-AutodiscoverVirtualDirectory "DC-server\Autodiscover (Default Web Site)" -WSSecurityAuthentication:$True
Set-AutodiscoverVirtualDirectory -Identity ‘autodiscover (Default Web Site)’ –WSSecurityAuthentication $true

i`ve also enabled Outlook Anywhere.

My server runs on windows server 2012 R2

Error message
Joris DijkAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shreedhar EtteCommented:
Hi Joris,

- Make sure you are able to access the URL "https://autodiscover.contoso.com/autodiscover/autodiscover.svc/WSSecurity" externally.

- Make sure you internal DNS is not blocking forwarding. Also Add an A record for the Autodiscover URL Autodiscover.contoso.com to the internal DNS record, and then point that record to the on-premises Client Access server.
Ganesh GuruduSenior ConsultantCommented:
We can run EXRCA(https://testconnectivity.microsoft.com/) report to ensure the Autodiscover is working properly externally.
From the Internet, you can also test Autodiscover for your domains:
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
After authenticating, if you get XML with a 600 error and no certificate warning, it's a good sign that it's working.
Make sure that WSSecurity is properly enabled on the Autodiscover virtual directory.
Make sure the domain autodiscover records are list in your internet published certificate.
What’s more, please help to connect the HCW log (location: %appdata%\Microsoft\Exchange Hybrid Configuration) to find more information about this issue.
refer : https://social.technet.microsoft.com/Forums/windows/en-US/59604c51-894d-4ab3-a9bf-ed54cd7c3a08/hcw8057-office-365-was-unable-to-communicate-with-your-onpremises-autodiscover-endpoint?forum=onlineservicesexchange

And also check the below URL
https://community.spiceworks.com/topic/2034346-hcw8057-office-365-was-unable-to-communicate-with-your-on-premises-autodiscover
Joris DijkAuthor Commented:
Hi,

i can access The URL "https://autodiscover.contoso.com/autodiscover/autodiscover.svc/WSSecurity" externally.

And ive had already added the autodiscover.contoso.com to my internal dns.


the problem still occurs
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Joris DijkAuthor Commented:
HI

Ive done the conectivety test and ive get the following results everything is green and there is one warning the warning says:

Certificate trust is being validated.
       The certificate is trusted and all certificates are present in the chain.
       
      Test Steps
       
      The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.contoso.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated.
       One or more certificate chains were constructed successfully.
       
      Additional Details
      Analyzing the certificate chains for compatibility problems with versions of Windows.
       Potential compatibility problems were identified with some versions of Windows.

ive also checked the https://autodiscover.domain.com/Autodiscover/Autodiscover.xml and get the 600 error message.
Shreedhar EtteCommented:
Hi Joris,

I didn't verfied the HCW snapshot properly.

You can safely ignore this warning and you can test the migration functionality by moving a test mailbox to office 365.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MaheshArchitectCommented:
you can rerun the hybrid config wizard and it should get completed without errors
As some times O365 federation gateway need some time to validate onpremise federation certificates which are generated during HCW process
Ganesh GuruduSenior ConsultantCommented:
contact Office support directly.

i feel this is not the issue,  you can ignore this warning .
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.