When trying to configure AD Quest Application Configuration (QAC) error 4 is encountered.
Example of commands:
/opt/quest/bin/vastool configure ad -d example.com
/opt/quest/bin/vastool configure ad -d example.com "cn=qas,dc=example,dc=com"
ERROR:
Error creating QAS application configuration (error 4).
ERROR: VAS_ERR_LDAP: Error encountered processing ldap result for dn [CN={XXX},CN=Authentication Services,CN=Quest Software,CN=Program Data,DC=example,DC=com], err=0000208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
'DC=example,DC=com'
.
Caused by:
LDAP_NO_SUCH_OBJECT: No entry found on server
The path to the object exists in AD and permissions seem correct.
CAUSE 1:
"OU=Program Data" was manually created at some point when VAS needs "CN=Program Data" and so VAS is unable to create the object.
CAUSE 2:
The distinguished name specified used CN=qas in the command when it should of been OU=qas
RESOLUTION 1:
Delete the OU "Program Data" and replace it with CN, then the "vastool configure ad" command will work.
RESOLUTION 2:
Check that the distinguished name of the object is correct. Check to see if the path contains containers (CN) or organizational units (OU).
TROUBLESHOOTING:
Add the -d5 option to the command to get debug and pipe to a file to attach to a Service Request for further assistance:
/opt/quest/bin/vastool -d5 configure ad -d example.com "cn=qas,dc=example,dc=com" 2>&1 | tee /tmp/qac-create-fails.txt
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center