Article - CS121970
Unable to access Integrity Server due to missing LDAP attribute for a user
Modified: 25-Aug-2018
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 2009 9.6 to 11.2
Description
- If a user object in the backing directory does not have a value for one of the attributes Integrity queries on, the Integrity Server will not start.
- Note that in some occurrences of this problem, a proper error message may not appear in the Integrity Server log
- You may however observe something similar to the following line in the server log with LDAP logging enabled:
- LDAP(10): Context: java.naming.batchsize=100, java.naming.security.authentication=simple, java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory, java.naming.referral=throw, java.naming.provider.url=ldap://domain_Controller_name.Domain.com:389, java.naming.security.principal=ldap_principal_name, com.sun.jndi.ldap.connect.pool=true, com.sun.jndi.ldap.connect.timeout=5000, java.naming.batchsize=100
- ldap_principal_name refers to the value of the ldap.principal property in the <IntegrityServerInstallDIR>/config/properties /security.properties
- This will be the last thing logged to the server before it begins it's shutdown process
- Shutdown process is signaled by generic failures in the server log such as * * * * ERROR * * * * (0): Shutdown requested by Configuration service. Reason: Unable to startup Security Service: Service mks:name=Authorization not started due to errors: null
This is a printer-friendly version of Article 121970 and may be out of date. For the latest version click CS121970