- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2022 11:47 PM
Anyone else having issues with LDAP after upgrading to San Diego? We just upgraded and now LDAP doesn't work:
When running a Test Connection on the LDAP Server the following messages are displayed
Error Messageldap://xxxxx.xxxxxxxxxx.xxx.xx:389/ Invalid credentials
Make sure this user account has login and read access to the server
Verify password
And in LDAP Listener Status the last error details are
Exception while connecting to LDAP Server, [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090447, comment: AcceptSecurityContext error, data 52e, v3839]
The User name and password are correct as we can use them to logon to the MID Server via RDP
Solved! Go to Solution.
- Labels:
-
MID Server
-
Orchestration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2022 04:27 PM
We were able to resolve this issue.
Our UAT instance was working fine.
This issue was only occurring in our Prod instance. We ascertained the credentials we were entering into LDAP were correct, so we rebooted both of our PROD MID Servers.
This resolved the issue and LDAP is running correctly now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2022 09:01 AM
We are experiencing this issue as well. The credentials are all valid, and these are the same used in our other instances. This instance keeps causing the credentials to lock in AD after enabling the listener. This is only occurring on 1 of the 3 instances that were upgraded to San Diego Patch 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2022 12:02 PM
Just to follow up what fixed this for us. After our upgrade to San Diego Patch 2, LDAP in ServiceNow was not working. Re-entering the credentials multiple times manually did not help. Deleting the server settings and manually re-doing them did not work. The fix ended up being needing to restart the MID server we were using for LDAP. Even though the other instances were working fine with regard to LDAP, each instance runs it's own MID Server service. I probably could have just restarted the service running specifically for the affected instance, but we just went ahead and rebooted the server for good measure. After the reboot and services started back up, LDAP connectivity was restored. Test connections worked perfectly.
I hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2022 07:03 PM
I've been getting the credentials error also since San Diego upgrade. Same account and settings works on other instance no issues. Mid server restarted, credentials redone and confirmed but no luck so far. Might go to latest patch and see if that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2022 09:03 AM
I had same issue after San Diego upgrade. It did require restarting the MID server after re-entering the user and password. The MID Server did not restart gracefully. We had to manually run the start.bat.
But after MID server came back, everything was working for LDAP connection
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2022 02:56 PM
Hi Ned,
After upgrade my mid lost UiPath certs but I fixed that and otherwise it's running fine. I've restarted the the mid and it thinks it's running fine but ldap is no go. Manually doing credentials has not helped and neither has a full restartof the box a few times. Guess it can't hurt to try the start.bat again though.
