Issues with LDAP Listener after Tokyo Upgrade

[Suzanne4]

Since we upgraded to Tokyo, the LDAP listener is not picking up new users or updates.  We have it set to update every 5 minutes, but it is taking hours and hours.  If we restart the listener, it works for a short time, but then goes back to hours and hours before we get updates.  This is greatly impacting our Onboarding and Transitions process.  Our LDAP integration is fine as our scheduled imports are working each night.  Not an LDAP or MID Server issues that we can tell at this point.  We opened a case with NOW Support 15 days ago.  We are going back and forth and they are just "guessing" at how to fix it.  This is quite frustrating.  Has anyone else experienced this issue and found a true solution?  Much appreciated!

[Allen Andreas]

Hi,

I haven't seen any posts related to LDAP listeners having an issue since Tokyo or in general. I'll definitely take a look through and see if I specifically see something.

In terms of the next appropriate step, you've done that by submitting a case to SN Support. The listener is dependent on the host and there may have been some sort of issue after the upgrade that caused this to occur. As far as SN Support "guessing" have they asked for access to your environment to help look at things?

Do you have LDAP active on any other environments? Are you having the same issue on those as well? (as they'd require separate MIDs anyway so this would help give you different test cases).

When you say it stops working, what error, if any, do you see?

Can you give more information as to what SN Support has suggested to try? So we don't recommend anything you've already heard.

Thanks!

[sandirileyokc]

Hi Suzanne, we are having the same issues. The account continues to lock out after a time. This did not happen before Tokyo and we too do not have consistent updates to our user accounts.