LDAP: error code 65 - Object Class Violation on FullName attribute
search cancel

LDAP: error code 65 - Object Class Violation on FullName attribute

book

Article ID: 229699

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

After Parallel upgrade, you get this error, it still works as expected in Legacy but fails in the New IDM setup.

The error we see in LDAP is CN is not getting updated, hence the error.

21:24:14,642 ERROR [ims.llsdk.directory.jndi] Failed to create managed object ObjectType::USER with unique name uid=p******,ou=people,dc=****,dc=com Error message from the directory: [LDAP: error code 65 - Object Class Violation]
21:24:14,644 ERROR [im.provisioning] [LDAP: error code 65 - Object Class Violation]
21:24:14,644 ERROR [com.netegrity.ims.exception.EventExecuteStateException] Execution of event: CreateUserEvent failed. Exception encountered: [LDAP: error code 65 - Object Class Violation]

 

Environment

Release : 14.4

Component : IdentityMinder(Identity Manager)

Cause

In one of the new14.4 environments the FullName LAH was apparently not firing even though it appeared to be enabled in the Management Console. It works fine another 14.4 environment. There may be some corruption in the LAH definition in the Object Store.

Resolution

Delete the FullName LAH in the Management Console.

Restart the Environment.

Re-add the FullName LA via the Management console.

Restart the Environment.