EEM upgrade fails with error [CAUAJM_W_112133] Unable to install or upgrade the CA EEM server.

Products

• Autosys Workload Automation

Issue/Introduction

When running AutoSys installer to upgrade EEM on a standalone EEM server, it errors out, below messages are see in the cawa_installer.log file

2026-01-25 06:26:12,499 [main] DEBUG com.ca.wla.ae.installer.util.CommandUtil(130) - RetVal =254
2026-01-25 06:26:12,499 [main] INFO  com.ca.wla.ae.installer.mm.action.eem.InstallEEM(165) - EEM Upgrade exit code ...254
2026-01-25 06:26:12,500 [main] WARN  com.ca.wla.ae.installer.logger.LogHelper(52) - NonFatalException : W_AE_EEM_Failed_Installation_Error [CAUAJM_W_112133] Unable to install or upgrade the CA EEM server.

 

To remove AutoSys installer from picture, running the EEM upgrade manually using <AutoSysISO>/modules/EEM/setup  gives an error about sanity check failed because local hostname and DNS name are not matching. This is specially true on AWS ec2 instances, where external name is different from EC2's internal name which is of the format  ip-###-###-###-###.ec2.internal

23 Jun 2025 06:32:44 INFO  SanityCheckAction - Local hostname name is eemserver.example.com
23 Jun 2025 06:32:44 FATAL SanityCheckAction - Local hostname name is eemserver.example.com and DNS hostname is ip-###-###-###-###.ec2.internal  Hostnames dont match

echo $?      showed 254   which explains why AutoSys upgrade was failing with that error code.

 

Resolution

• Change the local hostname (temporarily) to match DNS name, just for upgrade or install purpose

sudo hostnamectl set-hostname ip-###-###-###-###.ec2.internal

• Re-run the AutoSys installer to install/upgrade EEM.
  
  
• Once the install/upgrade is done, change the hostname back to what it was before

sudo hostnamectl set-hostname  eemserver.example.com 

 

Additional Information

EEM installer will be enhanced in a later release, to remove this limitation