CAUAJM_E_10436 Security server unreachable or invalid authentication certificate file.

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• CA Workload Automation AE

Issue/Introduction

We are having the following issue this morning, when attempting to issue any commands in Autosys (12.0)   

jr %CAUAJM_E_10029 Communication attempt with the AutoSys Application Server has failed! [host1234:9000]

CAUAJM_E_10436 Security server unreachable or invalid authentication certificate file.

CAUAJM_E_10434 Error initiating security session. [EE_BADOBJECT Bad Object] [ISE_BACKENDDOWN backend is down] [Attach Error: PozError] [PE_SPONSORERROR iSponsor Error] [pozFactory::attachPoz: error invoking iPoz::ClientAttach on host host1234] [attach failed] [ISE_BACKENDDOWN backend is down] [pozFactory::attachPoz: error invoking iPoz::ClientAttach on host host1234] [attach failed] [ISE_BACKENDDOWN backend is down] [WorkloadAutomationAE] [CERT-WorkloadAutomationAE] [CertificateReader::loadPEM  - cannot read certificate]  

Also the EEM UI's application drop down list shows only Global, it is missing WCC0004 and WorkloadAutomation AE.

Environment

Release : 12

Component : CA Workload Automation AE (AutoSys)

Resolution

Typically if the EEM UI drop down list is empty the dxserver process is not running or is running but has errors.

For Windows the
CA Directory - itechpoz
and
CA iTechnology iGateway 4.7
services should be set to Automatic startup.

For *UX
If you have your system configured to start EEM at boot time you should have
/etc/init.d/dxserver
Which is a script and there would be an entry like the following in the file:
# Default-Start: 2 3 5
Additionally you would have the following that are all links to /etc/init.d/dxserver
/etc/rc.d/rc2.d/S99dxserver
/etc/rc.d/rc3.d/S99dxserver
/etc/rc.d/rc5.d/S99dxserver
And in /opt/CA/SharedComponents/CADirectory/dxserver/config/autostart you would have a zero byte file named itechpoz

and for igateway:
/etc/init.d/igatewayd
and
/etc/rc.d/rc2.d/S99igateway
/etc/rc.d/rc3.d/S99igateway
/etc/rc.d/rc5.d/S99igateway
which are links to $IGW_LOC/S99igateway.

The most common reason a process does not start at boot time is either the port was not available to somehow the environment was not set correct.
Example: the dxserver script could not su to the dsa user and consume the variables like $DXHOME.

If needed, review the EEM configuration files and logs for more details:

$CASHCOMP/EmbeddedEntitlementsManager/eiam-install.log

$CASHCOMP/EmbeddedEntitlementsManager/config/server/server.xml

$CASHCOMP/EmbeddedEntitlementsManager/logs/*

$CASHCOMP/CADirectory/dxserver/config/knowledge/*

$CASHCOMP/CADirectory/dxserver/logs/*

$CASHCOMP/iTechnology/*.conf

$CASHCOMP/iTechnology/*.log