-
タイトル
DirSync: Agent Error connecting to endpoint: The LDAP server is unavailable. (Discovery failing) -
説明
There is an issue with Directory Sync CDS Discovery failing on a Local Environment with the error logged below:62415,950,target2016,Discovery: Connecting to Domain Controller using port: 389,,7/29/2021 10:24:12 AM
62416,950,target2016,Discovery: Error connecting to endpoint: The LDAP server is unavailable.,"System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable.
at System.DirectoryServices.Protocols.LdapConnection.Connect()
at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential)
at CDS.Model.DomainController.Connect(NetworkCredential credentials, Int32 port)
at CDS.Model.ActiveDirectory.Connect()
at CDS.Model.Agent.ExecuteJobs(CancellationToken cancellationToken)",7/29/2021 10:24:13 AM -
原因
POSSIBLE CAUSE 1
This error occurs when IPV6 is disabled on the Agent Server.
POSSIBLE CAUSE 2
Something is wrong with the domain controller (dc)
Possible Cause 3
Issue with the service account
Possible Cause 4
The Domain Controller IP address changed and the IP Address stored in our SQL db is incorrect -
対策
For POSSIBLE CAUSE 1
Enable IPV6 on the Agent Server, and restart the Directory Sync Agent Service on the agent server and rerun DiscoveryFor POSSIBLE CAUSE 2
Add a second domain controller. pdc. To the other tenant side for which you've been working. Perhaps you will have better success connecting to the other one (dc). Afterwards the first workflow run can take a much longer time than usual to complete. An extended runtime is to be expected if the jobs have been failing for a while. Need to catch up.
For POSSIBLE CAUSE 3
Ensure that the service account is a direct member of domain admins and not a member of a group which has been added to domain admins
For POSSIBLE CAUSE 4
Uninstall the Dirsync agent in the specific environment causing this issue.
From Dirsync Environment create a New Agent, install the agent on the agent server, and use the new registration ID.
If this does not resolve the issue, click this link and request Support run a remediation to update the IP address in the DomainControllers SQL db
Provide the Environment name
Server Fully Qualified Domain Name (FQDN)
Server IP Address
Contact Support