Provisioning Job Failing : Error code 65

[mirani]

Greetings,
I am facing an error while requesting for an AD app and unable to resolve it.
The account gets provisioned but not the groups/entitlements with it.

The error is displayed in comments of the pending task.
 Existing comments : [02-21-2024 14:03:23 UTC -XXXXXX Mirani (XXXXXXX)] test Account Key already exists for the account name. Setting Accountkey in for the Task.

Provisioning Comments : Error while ADD operation for account-XXXXXXX to Group-CN=XXX,ou=XXX,ou=Groups,dc=XXX,dc=com in AD - [LDAP: error code 65 - Entry 'CN=XXX,ou=XXXs,ou=Groups,dc=XXX,dc=com' cannot be modified because the resulting entry would have violated the server schema: Entry 'CN=XXX,ou=XXX,ou=Groups,dc=XXX,dc=com' violates the Directory Server schema configuration because it includes attribute '' which is not allowed by any of the object classes defined in that entry]

When I am requesting for other endpoint which is configured under same connection,  it is working fine. So the connection or the json's are also not the issue.
Getting this error for this particular endpoint only. Compared both the endpoints to check and see if any config is missed, but that is also not the case.

Want to know what is causing this error and how to resolve it.

[CR]

@mirani  already accountname and key it available , can you try different name(re-name it accountname)

or

Endpointkey = 65  check already account available ,make it as suspend  then try new request

accountname :CN=XXX,

Error : it LDAP: error code 65 - Entry 'CN=XXX,ou=XXXs,ou=Groups,dc=XXX,dc=com

[Manu269]

If you receive an LDAP error code 65 while attempting to create a user, it indicates that you did not correctly prepare the identity repository. Error code 65 is an LDAP object class violation and often indicates a problem with the directory schema or permissions.

[rushikeshvartak]

You have data issue with accountid and name in particular table. check there are no duplicates