Problems with the ECLI running commands on autosys server results in Command not found or could not execute.

book

Article ID: 39477

calendar_today

Updated On:

Products

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

Issue/Introduction

Introduction: 

Problems with the ECLI running commands on autosys server results in Command not found or could not execute.

 

Question: 

When tired to execute an AutoSys command from the ECLI got an error indicating the command could not be executed. 

In WCC CommandApp.log, we found the following message: 

com.ca.uejm.command.client.autosys.AutoSysCommandClient IclException while calling sponsor 404 Error 

 

We tried restarting igateway. It did not help. 

 

 

Environment:  

11.1 through 11.4.x on All platforms of WCC

 

Answer: 

Restarting the Application server helped restore the connection between WCC and the Autosys Application server.

Environment

Release: ATSAGE99000-11.3-Workload Automation AE-Remote Agent
Component: