WCC : ECLI unable to import or use client commands. Output: The command could not be executed. Command processing exception encountered.

book

Article ID: 105829

calendar_today

Updated On:

Products

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

Issue/Introduction

 When using ECLI to import Job Definitions, or execute a client command such as autoping the Output area shows:
----------------------------------
The command could not be executed. Command processing exception encountered. 

Errors: 
java.net.ConnectException: Connection refused: connect
-------------------------------------

Cause

The install of the Command Sponsor may not have initially been complete.

Environment

AE: 1589 Windows_NT ORA 11.3.6 SP7  
 
WCC:  11.4.6.20180302-b425 

Resolution

When using ECLI requests are sent to the Command Sponsor using iGateway.  The Command Sponsor is normally installed with AE.  The Command Sponsor requires the iGateway to be up. In this case,  iGateway would not start, it would only stay in a 'starting' state and never change.  The iGateway.log did not show anything meaningful. The iGateway.log was renamed and the service started again and nothing appeared in the log.

Using the AE Media, the 'Repair' option was chosen for CA Workload Automation AE.  After this completed, the services were restarted.  iGateway started on the Scheduler machine.  

In WCC, using ECLI the import and client commands were successful.