000015522 - AXM6.1 - ADAM standalone   eserver fails to start on search for AdminSequence

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 Number000015522
Applies ToAccess Manager 6.1
Microsoft ADAM with SP1
IssueAXM6.1 - ADAM standalone , eserver fails to start on search for AdminSequence

 Eserver failed to start on first query of Access Manager with "AdminSequence not found"

Using Netscape debug tracing  the following query and result was observed.

16:31:49:548 [*] [main] - LDAPReservedSequenceFactory.getSequence("AdminSequence") 16:31:49.564 ldc=29 op=61 SearchRequest {baseObject=ou=ctscApplicationDataRepository,ou=AxM,dc=dowjones,dc=net, scope=1, derefAliases=0,sizeLimit=1000, timeLimit=0, attrsOnly=false, filter=(&(objectclass=ctscReservedSequence)(cn=AdminSequence)), attributes=null} 16:31:49.564 ldc=29 op=61 SearchResult {resultCode=32, matchedDN=OU=AxM,DC=dowjones,DC=net, errorMessage=0000208D: NameErr: DSID-031521D2, problem 2001 (NO_OBJECT), data 0, best match of:

CauseThe user for the LDAP bind to ADAM did not have sufficient roles.
ResolutionAdding the bind user to an administrator role in Adam fixed the issue.
Right-click on the Readers container in Roles and select properties?
Scroll down the list of attributes to Member and click Edit
Click on ?Add ADAM Account??
Enter the dn for the bind user account
Legacy Article IDa51583