LDAPProbeError with LDAP MID server configuration yet manually testing the connection works.

danbowman
Kilo Contributor

        When viewing System LDAP > LDAP Servers the related link for "Test Connection" comes back as "Connected Successfully", and we are able to browse any OU definitions yet the MID server LDAP probe fails.

Has anyone seen this before?

It is really odd because even the LDAP Monitor shows the listener as active and picking up changes. Only scheduled loads appear to be disrupted, and are returning LDAPProbeError on the ECC Queue.

Here is the error message from a test load of 20 records:

Screenshot_083117_044319_PM.jpg

Here are the error messages from the failed probe:

Screenshot_083117_044500_PM.jpg

Screenshot_083117_044518_PM.jpg

Everything appears to be configured correctly.

Thank you for taking the time to read through this, and any feedback is appreciated.

1 ACCEPTED SOLUTION

corina
ServiceNow Employee
ServiceNow Employee

Hello Dan.



Thsi could go way with reinstalling the MID server.



Otherwise check the ACL for the ldap_ou_config and ldap_server_config tables, sys_data_source for mid_server


View solution in original post

2 REPLIES 2

corina
ServiceNow Employee
ServiceNow Employee

Hello Dan.



Thsi could go way with reinstalling the MID server.



Otherwise check the ACL for the ldap_ou_config and ldap_server_config tables, sys_data_source for mid_server


corina
ServiceNow Employee
ServiceNow Employee

If the ACL is the reason, most probably you will be able to see this in the MID server logs.