Description #1
While trying to Unix Enable an User account from the command line you might see an error message similar to this:
Failed to unix enable user: testuser
ERROR: VAS_ERR_FAILURE: Unspecified failure
Caused by:
VAS_ERR_LDAP: Error encountered processing ldap result for dn [CN=Test User,OU=User,DC=example,DC=com], err=00002082: AtrErr: DSID-0315109A, #1:
0: 00002082: DSID-0315109A, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 54b50000 (uidNumber):len 4
Caused by:
LDAP_CONSTRAINT_VIOLATION: No LDAP error string defined for LDAP error code: 19
Description #2
While trying to join a host to the domain an error is generated.
VAS_ERR_LDAP: Error encountered processing ldap result for dn [CN=computername,CN=Computers,DC=example,DC=com], err=0000207C: AtrErr: DSID-03152CAF, #1:
0: 0000207C: DSID-03152CAF, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 3 (cn)
.
Caused by:
LDAP_CONSTRAINT_VIOLATION: No LDAP error string defined for LDAP error code: 19
Description #3
While trying to assign an account to an attribute in AD an error is generated.
Cause #1
If an attribute's properties are set with minimum and maximum values and you are trying to create a user with a UID or GID outside of that range you will trigger this error message.
Cause #2
The error can also be caused when trying to set an attribute value on a computer object like DN when there are insufficient permissions during the join
Cause #3
Some attributes in AD require a DN be provided when being set
Resolution for Problem #1
1. Define the UID or GID to be within the specified range within the Active Directory Schema when enabling the account.
2. Modify the acceptable ranges.
Resolution for Problem #2
1. Use an account with sufficient permissions to join and write to the computer object.
2. Give the current account sufficient permissions to join and write to the computer object.
Resolution to Problem #3
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center