000037824 - After restarting RSA Identity Governance & Lifecycle, the browser shows an Initialization Status screen with connection errors and users are unable to login

Document created by RSA Customer Support Employee on Aug 9, 2019•Last modified by RSA Customer Support Employee on Aug 14, 2019
Version 3Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000037824
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: All
 
IssueAfter an RSA Identity Governance & Lifecycle restart, users are unable to login to RSA Identity Governance & Lifecycle. Instead of the login screen the browser shows an Initialization Status screen with the following messages and errors:
  • Initialization operations completed. Server is ready to accept requests.
  • Unable to get avdb connection to check for data re-encryption. Verify that the database is available and a connection to the avdb database can be made with the avuser credentials.
  • Unable to make avb connection. Verify that the database is available and a connection to the avdb database can be made with the avuser credentials.
  • Unable to make avdwdb connection. Verify that the database is available and a connection to the avdwdb database can be made with the avdwdb credentials.
  • Unable to make acmdb connection. Verify that the database is available and a connection to the acmdb database can be made with the acmdb credentials.

 User-added image


The aveksaServer.log has the following errors:
 
06/26/2019 21:06:39.722 INFO  (MSC service thread 1-64) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization Start ********************
06/26/2019 21:06:40.930 ERROR (MSC service thread 1-64) [com.aveksa.migration.jdbctool.CheckDatabase] Unable to make avdb connection
java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jdbc/avdb
        at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:154)
        at com.aveksa.migration.jdbctool.CheckDatabase.initDBConnection(CheckDatabase.java:408)
        at com.aveksa.migration.jdbctool.CheckDatabase.check(CheckDatabase.java:475)
        at com.aveksa.server.runtime.AveksaSystem.initialize(AveksaSystem.java:309)
        at com.aveksa.init.Startup.init(Startup.java:52)
 


 

Please refer to  RSA Knowledge Base Article 000030327 -- Arifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment. 
CauseBy default RSA Identity Governance & Lifecycle connects to the Oracle database using listener port 1555. This error can occur if the listener port is inadvertently modified to 1521 (Oracle default) or some other port number prior to the restart.

NOTE: The port change does not take affect until RSA Identity Governance & Lifecycle is restarted so the port modification may have occurred some time before the incident. It is the restart that triggers the connection errors. 
 
ResolutionRoll back the port change by modifying the listener port back to 1555 and restarting RSA Identity Governance & Lifecycle.

Note: If you are getting these errors and have not modified the listener port, please refer to related RSA Knowledge Base Article 000036785 -- RSA Identity Governance & Lifecycle fails to start with "Unable to get avdb connection" message for additional assistance.

Attachments

    Outcomes