Error: NoClassDefFoundError starting EEM Reporting Utility after AutoSys or EEM upgrade

Products

• Autosys Workload Automation

Issue/Introduction

When attempting to start the EEM Reporting Utility (ERU) after upgrading AutoSys to R24.1 or EEM to 12.7.x, the service fails to start. The following errors may appear in the logs:

 

 

Error: Unable to initialize main class com.ca.eiam.audit.AuditToolCaused by: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException

Or:

 

 

WrapperJarApp Error: java.lang.NoClassDefFoundError: javax/xml/bind/PropertyExceptionCaused by: java.lang.ClassNotFoundException: javax.xml.bind.PropertyException

Environment

• AutoSys Workload Automation R24.1 and higher
• Embedded Entitlements Manager (EEM) 12.6.x, 12.7.x
• EEM Reporting Utility (ERU)

Cause

The EEM Reporting Utility is not upgraded automatically during an AutoSys or EEM upgrade.
ERU versions are not cross-version compatible because they rely on specific Java runtimes (e.g., ERU 12.6.x uses Java 8, while ERU 12.7.x/24.1 uses Java 11 or 17).

If an older version of ERU remains on the system after an EEM upgrade, it will fail to initialize due to missing or incompatible Java classes.

Resolution

Install the version of the EEM Reporting Utility that matches your current EEM version.

1. Locate the ERU installer on your product media. For AutoSys R24.1, it is found in the ISO under: AutoSysLIN24.1.01.iso\modules\ERU\
2. Run the ERU installer post-upgrade to ensure compatibility with the new EEM version.
3. Verify the wrapper.java.command in .../conf/wrapper.conf points to the correct JRE path provided by the new installation.
4. Restart the EEM Audit Reporting Service.

For detailed installation steps, see install the CA EEM Reporting Utility.