locked
Azure AD connect pass through issue RRS feed

  • Question

  • I have installed latest version 1.1.614 of azure ad connect. Syncing is working older version was also working

    in fiddler  getting this <input type="hidden" name="error_description" value="AADSTS70002: Error validating credentials. AADSTS80001: No Microsoft Azure AD Connect Authentication Agent was found. Make sure that your environment is configured correctly. If your directory is set for pass-through authentication, make sure that your Microsoft Azure AD Connect Authentication Agent is online.

    Trace ID: 78ee5a6b-d9a7-4207-a8f4-0ac1f4a01200

    Correlation ID: 2464b18a-56c1-48cb-8e32-d13f8c4848ae

    Timestamp: 2017-09-15 12:24:34Z" /><

    on the machine AzureADConnectAuthenticationAgentService.exe Error: 0 : UpgradeProxyTrustSettingsLocation: Cannot start connector service since the connector is not registered.
        ThreadId=1
        DateTime=2017-09-15T11:00:59.7313201Z
    AzureADConnectAuthenticationAgentService.exe Error: 0 : Unhandled exception was thrown in Main: 'System.Configuration.SettingsPropertyNotFoundException: ProxyTrustCertificateThumbprint
       at Microsoft.ApplicationProxy.Connector.Common.Runners.ServiceRunner`1.UpgradeProxyTrustSettingsLocation()
       at Microsoft.ApplicationProxy.Connector.Common.Runners.ServiceRunner`1.Run(String[] args, ITracingHelperLogger logger)'
        ThreadId=1
        DateTime=2017-09-15T11:00:59.7632388Z after  I manually copied the thumbprint from config to registry I am getting

    AzureADConnectAuthenticationAgentService.exe Error: 0 : Signaling Service Host is closing

    Friday, September 15, 2017 12:28 PM

Answers

  • We found a service side issue and fixed it.

    Thank you for reporting and “sorry for the inconvenience”.

    -----------------------------------------------------------------------------------------------------------------------------------
    Do click on "Mark as Answer" on the post that helps you and vote it as helpful, this can be beneficial to other community members.

    • Marked as answer by som nath Monday, September 18, 2017 7:42 AM
    Monday, September 18, 2017 3:08 AM

All replies

  • The error during the authentication request, which indicated that the on-prem agent is not available, was caused by a mis-configuration on our end and we are currently working on fixing it. Stay Tuned.

    ---------------------------------------------------------------------------------------------------
    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    Saturday, September 16, 2017 6:02 AM
  • The fix for the issue has completed. Suggest you to try to authenticate again and check.

    ---------------------------------------------------------------------------------------------------
    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    Saturday, September 16, 2017 9:28 AM
  • let me know when new installer is available.
    Saturday, September 16, 2017 2:12 PM
  • thanks it works. where was issue. on premise side or azure side. and how you have deployed the fix.
    Sunday, September 17, 2017 3:33 AM
  • We found a service side issue and fixed it.

    Thank you for reporting and “sorry for the inconvenience”.

    -----------------------------------------------------------------------------------------------------------------------------------
    Do click on "Mark as Answer" on the post that helps you and vote it as helpful, this can be beneficial to other community members.

    • Marked as answer by som nath Monday, September 18, 2017 7:42 AM
    Monday, September 18, 2017 3:08 AM