Q: |
Error finding LDAP name of group '<DOMAIN>\CS716' (pre-Windows 2000 name). No results found searching 'LDAP://<DOMAIN>'. |
| A: | User Management Resource Administrator searches the Global Catalog for the LDAP name of this group. Make sure the group exists and the GC is updated before running the project. |
Q: |
Error 3 writing export file C:\<path>\<filename>.txt |
| A: | Make sure the path of your export file is correctly defined in the export variables script action. |
Q: |
Error 2453 translating domain name <DOMAIN> to LDAP format. Cannot determine domain controller. |
| A: | Make sure the domain can be contacted using your DNS provider. |
Q: |
License violation error in action 'Get user attribute (AD)'. Script and session terminated. |
| A: | User Management Resource Administrator needs a valid license for all script actions to execute. Some actions require an additional license. |
Q: |
Error 0X80072116 (8470) converting name 'JSmith @constellations.com', from type 9 to 1 using binding type 1 (constellations.com). Cannot set input name. Name translation: Could not find the name or insufficient right to see name. |
| A: | When resolving the username, User Management Resource Administrator fails to retrieve the LDAP equivalent due to an additional space in the name which is not allowed. Make sure that when you are using names for import jobs, that all leading and trailing spaces are removed. You can use the format variable action to perform this operation. |
Q: |
Code 0x8000500d (20493) returned getting LDAP attribute 'description' from user object 'LDAP://CN=username,OU=TEST,DC=constellations,DC=com'. No attribute found, no error due to specification. The Active Directory property cannot be found in the cache. |
| A: | The attribute being searched for (description) is empty or does not exist in the Active Directory. This error can be expected and the script can continue its operation. |
Q: |
Error 0X80072030 (8240) finding AD account 'LDAP://CN=Name,DC=constellations,DC=com'. Cannot bind to object. There is no such object on the server. |
| A: | The object being searched for (user account) could not be found on the domain. Try specifying a domain controller in the appropriate script action or wait for the Active Directory to synchronize. |
Q: |
Error 0X8007054B (1355) finding AD account 'LDAP://CN=<FULL NAME>,OU=TEST,DC=constellations,DC=com'. Cannot bind to object. The specified domain either does not exist or could not be contacted |
| A: | The Active Directory could not be contacted. Check if your DNS provider has been configured correctly and try to specify a domain controller in the appropriate script action. As an alternative, you can try to use the username instead of the fullname to get a user account. |
Q: |
Error 0X80072030 creating AD account. Cannot access container object LDAP://<DOMAINCONTROLLER>/OU=Students,DC=constellations,DC=com. There is no such object on the server. |
| A: | The OU container could not be found, check if the Organizational Unit exists in the Active Directory. |
Q: |
Error 0X8007202F: Creating AD user account in container/OU 'LDAP://<DOMAINCONTROLLER>/CN=Users,DC=constellations,DC=com'. Cannot commit user 'John Smith' creation process. A constraint violation occurred. |
| A: | The Active Directory refuses to create the user account based on a constraint violation, meaning that certain attributes rules are broken. Examples of these rules are length limitations of certain attribute fields, such as the MiddleName (Initials) which can take only 4 characters. Also, make sure that the country attribute consists of the 2-character ISO code instead of the full country name. |
