000015611 - Access Manager eserver will not start.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000015611
Applies ToAccess Manager 6.1
IssueAccess Manager eserver will not start.

The eserver in debug mode shows the following exception.

14:44:03:077 [*] [main] - LDAPReservedSequenceFactory.getSequence("AdminSequence")
Unexpected DataStoreException
14:44:03:108 [*] [main] - Thread requesting stream.
sirrus.common.Server$InitializationFailedException: Unexpected DataStoreException
 at sirrus.api.server.AdministrativeAPIServer.initializeDatastore(AdministrativeAPIServer.java:265)
 at sirrus.api.server.AdministrativeAPIServer.main(AdministrativeAPIServer.java:147)


With search_profile=true the it shows the eserver fails on the first query executed:

Search: Base DN: ou=ctscApplicationDataRepository, dc=xxsupportlab7, dc=com Scope: 1 Filter: (&(objectclass=ctscReservedSequence)(cn=AdminSequence)) Attributes Only: false
Attributes: NULL
 Time: 16ms

CauseThis error indicates that the eserver is unable to read any information from LDAP.
ResolutionThe most common reason for this failure is that the user configured for the bind DN, cleartrust.data.ldap.directory.activedirectory.binddn=, does not have sufficient privilege to read the Access Manager database.  Modify the ACL's for the bind user so that it has read/write access to the datastore. 
Legacy Article IDa52824

Attachments

    Outcomes