LDAP sync issues

Team_Geek · 2022-02-25T20:08:58+00:00

There was an error rendering this rich post.

Hi,

Sorry if this is the wrong forum to post in but I'm looking for help with our Documentum software.

We sync users and groups from our Active Directory via LDAP sync job and this job has recently started failing. I'm seeing two main errors in the log but am struggling to resolve as I inherited the administration of our Documentum software and don't have a lot of experience supporting it.

First issue is processing group member and the error says "A user with user_login_name JohnDoe already exists in another domain in the docbase OurDocbaseName". From what I can tell, the original John Doe left the company, his AD account was deleted, and a new JohnDoe started with the same username.

The second issue still processing group membership and this error says "Cannot find user Smith, Jane; ERROCDE: 100". Jane Smith in this case got married and had a name change.

I suspect our helpdesk offboarded and renamed these accounts incorrectly and that is why the errors have started. How can I resolve these errors so our LDAP sync job completes successfully?

Find more posts tagged with

Comments

DCTM_Guru

There is a rename job in Documentum administrator. As for people with the same name, typically IT dept create new user logins for the users of the same name (ie JohnDoe1, JohnDoe2, etc), and deactivate the old one to avoid issues like this. Since your IT dept doesnt follow this convention, if you delete JohnDoe user account from docbase manually, LDAP sync job should "re-create" it and avoid this issue.

Team_Geek

Thanks for the help! That got me over the hump I had. I didn't realize you can delete the users without causing problems elsewhere. We were able to run the Reassign User task/job for the deleted users and the LDAP sync recreated them without errors now.

I found this post Renaming users - how dm_UserRename job works - EMC Documentum Answers (documentum-emc.blogspot.com) to rename the user that got married, and that took care of the other error message we had.