Issue with LDAP after upgrade to San Diego

bobd1
Tera Expert

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

1 ACCEPTED SOLUTION

bobd1
Tera Expert

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.  

 

View solution in original post

11 REPLIES 11

Community Alums
Not applicable

HI @bobd ,

After upgrade, you will need to feed your credentials again. so i recommend to enter your credentials.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

bobd1
Tera Expert

Hi Sandeep,
Thanks for the tip. By clearing both the Login name and the password and re-entering them, the LDAP Server connected successfully. 

However around 4 hours later the connection failed with this error message. 
Exception while connecting to LDAP Server, [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090447, comment: AcceptSecurityContext error, data 775, v3839]

I notice this time that there is a different code on 

 AcceptSecurityContext error, data 775

 

Community Alums
Not applicable

Hi @bobd ,

As per the error shared, it means the referenced account is currently locked out and may not be logged on to.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

bobd1
Tera Expert

Further update.

This error indicates the Service Account has been locked. This is being done by a process within ServiceNow as there is no other activity that would lock this account

AcceptSecurityContext error, data 775