Unable to log in to AAI 24.4 UI after upgrade - SafeException: EE_EXCEPTION at configureLogger

Products

• Automation Analytics & Intelligence

Issue/Introduction

After successfully upgrading to AAI 24.4, the following symptoms are observed:

• The AAI UI login page loads successfully.
• All AAI services appear to be running.
• Any attempt to log in fails with an authentication error.
• The server.log (located in jboss/standalone/log/) contains the following error stack trace:

 

[EIAMServiceImpl-11] ERROR com.termalabs.server.eem.EIAMUtils [] - unknown eEM problemcom.ca.eiam.SafeException: EE_EXCEPTION Exception    at com.ca.eiam.SafeConfigurator.configureLogger(SafeConfigurator.java:256)    at com.ca.eiam.SafeConfigurator.init_internal(SafeConfigurator.java:140)    at com.termalabs.server.eem.EIAMServerConnection.createContext(EIAMServerConnection.java:219)

Note: You may also notice the absence of the eiam.cppsdk.log file, which indicates the SDK is crashing before it can initialize network communication.

---

Environment

Product: Automic Automation Intelligence (AAI) 

Version: 24.4.x 

Component: AAI UI / EEM Authentication

Cause

 eiam.log4cxx.config failed to get copied to the /opt/Automic_Automation_Intelligence/dev_aai/jboss/standalone/configuration/ during the upgrade

Resolution

To resolve this issue, you must manually restore the missing configuration file:

1. Obtain the file: Locate the eiam.log4cxx.config file. This can be found in the AAI 24.4 installation/upgrade media under the /files/jbossRootOverwrite/standalone/configuration/ directory.  If you need help locating this file contact Broadcom Support
2. Copy the file: Copy eiam.log4cxx.config to the following location on the AAI Server:
   • Linux: /opt/Automic_Automation_Intelligence/dev_aai/jboss/standalone/configuration/
   • Windows: [AAI_Install_Dir]\jboss\standalone\configuration\
3. Verify Permissions: Ensure the AAI service user has read permissions for the newly added file.
4. Restart AAI: Restart the AAI/JBoss service to initialize the new configuration.

Verification

1. Attempt to log in to the AAI UI.
2. Check the logs to confirm the EE_EXCEPTION at SafeConfigurator.configureLogger no longer appears.
3. Confirm that eiam.cppsdk.log is now being generated in the log directory.