LDAP Errors / Warnings

[shawnroach]

Hi everyone! A client and I recently got their LDAP integration up and running. Almost everything seems to be working very well. However, we are getting the same two errors in the Error logs. They appear as often as every 4 to 5 minutes, and as far apart as 90 to 120 minutes. The messages in the error logs are:

LDAP exception validating object:Read timed out
LDAP exception validating object:LDAP response read timed out, timeout used:30000ms.

I cannot say for certain if these are the culprits, but we've had to restart the instance once due to Scheduled Jobs not running...choking.
I've dug deeper into the log entries and see no errors. These warnings are everywhere, though:

WARNING *** WARNING *** Invalid macro tag encountered: elevate_privilege
WARNING *** WARNING *** Invalid macro tag encountered: open_archive
WARNING *** WARNING *** Invalid macro tag encountered: domain_select
WARNING *** WARNING *** Invalid macro tag encountered: domain_reference_picker
WARNING *** WARNING *** Invalid macro tag encountered: encryption_select

Can anyone provide assistance and/or knowledge on this situation, please?

Thank you!

Shawn Roach | Technical Analyst
Fruition Partners | 200 S. Wacker Ste. 3100 Chicago, IL 60606
P: 816-616-7818 | shawn.roach@fruitionpartners.com
fruitionpartners.com | Trusted Advisors for IT Service Management

[itjudyhurst]

We've been having these same errors thrown daily.   Did you find a successful fix for these errors?   We're currently running Fuji Patch 5.   Not sure if when we request Fuji Patch 8 if these will be fixed, reading through the documentation it seems as though Patch 6 addressed a problem regarding the LDAP listeners (PRB633319).

Another thought...does anyone know how we can look though the Problems list that is current within ServiceNow?

[tony_barratt]

Hi Judy,

PRB633319 did address an issue with LDAP Listener when a MID Server is used.

It is fixed in FP6 and EP12.

If you are seeing errors in the LDAP logs consider creating a new thread on the Community - there are potentially lots of variables in LDAP configs so diagnosing errors may require details of the specifics.

Best Regards

Tony