08-06-2021 06:45 PM - edited 08-07-2021 12:23 AM
Hi All,
I have an issue with one user he is not synchronizing with LDAP, he is existing user not new user and he is never synchronized with cucm
I have collected dir sync logs and found below error,
DSDBInterface.updateUserInfo dbErrorNumber=19191
DSDBInterface.updateUserInfo For User :xxxxx DB ERROR: DiscoveryUserIdentity entered for EndUser already exists.
DSDBInterface.updateUserInfo User found with id xxxxx, but uniqids does not match (update uniqid)
I verified whether email id is configured for multiple users oor not, no luck.
Solved! Go to Solution.
08-07-2021 08:15 PM - edited 08-07-2021 09:15 PM
As @Roger Kallberg mentioned when syncing with AD, a loacl user with same end user details will be overwritten
DSDBInterface.updateUserInfo For User :xxxxx DB ERROR: DiscoveryUserIdentity entered for EndUser already exists.
Based on the error, There could be a local user who has has same DiscoveryUserIdentity
Run below command from CLI and see if any local user using the same DiscoveryUserIdentity. There could a LDAP user who has been converted to a local user with same DiscoveryUserIdentity as your new user.
DiscoveryUserIdentity will be your domain login-id.
run sql select u.userid,u.mailid,u.lastname,u.discoveryuseridentity from enduser as u order by u.discoveryuseridentity
I recreated your issue and I got the same error.
I synced AD, converted the ad user nithineluvathingal to a local user. On CUCM i changed the userid to google, from the below image you can see that the DiscoveryUserIdentity is still the same. And when i did a perform full sync i got below which is exactly your case.
2021-08-07 22:40:45,042 ERROR [DirSync-DBInterface] common.DSDBInterface (DSDBInterface.java:624) - DSDBInterface.updateUserInfo For User :nithineluvathingal DB ERROR: DiscoveryUserIdentity entered for EndUser already exists.
In your case find the user who use the DiscoveryUserIdentity same as your new User, delete this local user. SYNC AD. Then add the local user again.
08-06-2021 08:07 PM
Make sure the user belong to the same OU of the search base.
Second thing make sure the user has last name, if the use doesn't have a last name, he will not get synced.
08-06-2021 08:12 PM
All the ad configurations are good, but I found same user has same last name
Like
1 user : yenosh
2 user : yenosh.
Will it create any issue but second user has period .
08-06-2021 11:24 PM
Change the last name and see if those users are getting synced, I never come across a scenario where the last names are same and I have no access to my lab to test this now.
08-07-2021 12:22 AM
Thanks nithin,
I did remove the last letters for the other user as he is local user, I ll wait for next sync and let you know the status.
08-07-2021 12:43 AM - edited 08-07-2021 08:06 PM
No need to wait till the next sync, You can do a perform full sync from LDAP Directory.
To sync user, last name is mandatory.
08-07-2021 11:43 AM
If there is a local account that has exactly the same user credentials it would be overwritten by the directory synchronisation from AD.
As the users have similar, but not exactly the same, credentials it could cause issues as possible the dot might not count as a character that is valid in the last name.
08-07-2021 08:32 PM
Changing last name for other user did not work.
08-07-2021 09:16 PM
As @Roger Kallberg mentioned when syncing with AD, a local user with same end user details will be overwritten. Refer my previous Edited reply.
08-07-2021 08:15 PM - edited 08-07-2021 09:15 PM
As @Roger Kallberg mentioned when syncing with AD, a loacl user with same end user details will be overwritten
DSDBInterface.updateUserInfo For User :xxxxx DB ERROR: DiscoveryUserIdentity entered for EndUser already exists.
Based on the error, There could be a local user who has has same DiscoveryUserIdentity
Run below command from CLI and see if any local user using the same DiscoveryUserIdentity. There could a LDAP user who has been converted to a local user with same DiscoveryUserIdentity as your new user.
DiscoveryUserIdentity will be your domain login-id.
run sql select u.userid,u.mailid,u.lastname,u.discoveryuseridentity from enduser as u order by u.discoveryuseridentity
I recreated your issue and I got the same error.
I synced AD, converted the ad user nithineluvathingal to a local user. On CUCM i changed the userid to google, from the below image you can see that the DiscoveryUserIdentity is still the same. And when i did a perform full sync i got below which is exactly your case.
2021-08-07 22:40:45,042 ERROR [DirSync-DBInterface] common.DSDBInterface (DSDBInterface.java:624) - DSDBInterface.updateUserInfo For User :nithineluvathingal DB ERROR: DiscoveryUserIdentity entered for EndUser already exists.
In your case find the user who use the DiscoveryUserIdentity same as your new User, delete this local user. SYNC AD. Then add the local user again.
08-07-2021 08:34 PM
Thank you
I ll try this and let you know
08-10-2021 11:42 AM
Hi Nithin,
Sorry for delay in response, Today I have done this activity and it worked.
Thanks for all your effort and help.
Best Regards
Yenosh
07-20-2022 11:29 AM - edited 07-20-2022 01:37 PM
Hi @Nithin Eluvathingal ,
I am facing one similar issue. Might be you can help. Below is the summary:
User is using soft client Microsoft Lync/Jabber in Windows Desktop. When trying to login below error message appear:
The settings for the telephony configuration are invalid. Enter the username and password of the telephone services
In CUCM, User is synchronised via LDAP and using AD username and password to login.
And user have two user account in AD (not same: eg: User1, User2) with same password. And also same First Name & Last Name. And In CUCM, I can see both end user account Synchronised and available.
User is able to login in Self care portal using same AD username and password. And can see phone configuration also.
But getting error while login soft client. Any idea what could be the reason.
07-20-2022 01:15 PM - edited 07-20-2022 01:31 PM
I fail to see the connection between your Lynx client and CUCM. Can you please elaborate on this?
Apart from this it is not a good practice to ask an off topic question to the OP on an old post that is also marked as solved. It’s much better if you where to post your question on your own post.
07-20-2022 01:20 PM
They are using Microsoft CUCLyn soft client which is similar like Jabber in desktop. We can consider this as jabber.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide