getting ldap error DSID-031B0E6F, problem 5012 (DIR_ERROR), data 3

[venkat]

When we terminate a user. the account is moved to the disabled OU.  The below code works in dev and production.  The account has permissions to move the account to disabled ou and we verified the move permissions case.

In our test environment we are getting the above error

Error while Delete operation for account-xxxxx in AD, Error Deleting/Disablng the Account from AD - [LDAP: error code 80 - 00002089: UpdErr: DSID-031B0E6F, problem 5012 (DIR_ERROR), data 3 ]

Below is the code

{
"userAccountControl": "514",
"moveUsertoOU": "${if(user.customproperty32?.contains('Disable_Account') || user.customproperty36?.contains('LOA_START') || user.customproperty62?.contains('Disable User')) {user?.customproperty30+',OU=Admin,DC=xxx,DC=xxx,DC=net'} else {'OU=Disabled Users,DC=xxx,DC=xxx,DC=net'}}",
"description": "${if(user.customproperty32?.contains('Disable_Account') || user.customproperty36?.contains('LOA_START')){user?.locationdesc+'-'+user?.title} else if (user.customproperty62?.contains('Disable User')) {'Disabled as per request by HR/Management/Compliance on'+' '+new java.text.SimpleDateFormat('MM-dd-yyyy').format(new Date())+' '+'Need HR or Management approval to enable'} else {user?.customproperty35}}"
}

Any idea why we get the error

[rushikeshvartak]

Troubleshooting Steps:

1. Verify Permissions: Double-check the permissions in the test environment to ensure they match those in dev and production.

2. Check OU Paths: Ensure the target OUs are correctly defined and exist in the test environment.

3. Validate Custom Properties: Verify that the custom properties used in your code are set correctly for the test users.

4. Examine Logs: Look at the Active Directory logs or any application logs for more details about the error.

5. Test with Static Values: Temporarily replace dynamic values in the moveUsertoOU and description fields with static values to isolate whether the issue is with dynamic content or the move operation itself.

[stalluri]

Hello @venkat 

Check the value present in connection "SUPPORTEMPTYSTRING" mark it to FALSE.

If any of the custom properties (user.customproperty32, user.customproperty36, user.customproperty62) are null, the expression might fail or lead to unexpected results.

Also check the deatils as suggested below.