000030300 - Startup fails with 'The aveksa security application must be initialized first by the System Operations Node (SON)' error in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 10, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000030300
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 6.9.1 or earlier
 
IssueAfter upgrading RSA Identity Governance & Lifecycle, the following error is seen when starting the RSA Identity Governance & Lifecycle application:
 
Initialization has failed!
Unable to initialize security model. security Application not created.
The aveksa security application must be initialized first by the System Operations Node(SON).


This same error message is seen in the aveksaServer.log file located in:
$AVEKSA_HOME/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log/aveksaServer.log.
 
CauseThis error indicates that there is no System Operations Node (SON). We have seen this error when restoring a database from another system and migrating that database. The hostname of the other system remains in the table that stores the server nodes, T_SERVER_NODES. When RSA Identity Governance & Lifecycle starts, an entry in the table is made for both systems but the current node is not made the SON. The absence of a SON causes the aveksa application to fail to be deployed and this results in a failure of RSA Identity Governance & Lifecycle to start.
 
ResolutionThis issue may be resolved by truncating the T_SERVER_NODES table and restarting RSA Identity Governance & Lifecycle. Please see RSA Knowledge Base Article 000038542 -- How to restore the Server Nodes configuration in RSA Identity Governance & Lifecycle for instructions on truncating this table.
 
NotesPlease see related RSA Knowledge Base Article 000029739 -- Startup fails with 'com.aveksa.server.core.DuplicateNameException: Aveksa ADC' error when starting RSA Identity Governance & Lifecycle, if your error contains:
 
com.aveksa.server.core.DuplicateNameException:Aveksa ADC

Attachments

    Outcomes