search cancel

Why autoping is not working from a client/agent machine if autoping to the same machine from scheduler works and the cryptkey.txt files on the agent directory are the same?

book

Article ID: 42198

calendar_today

Updated On:

Products

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

Issue/Introduction

Introduction:

When trying to autoping an agent from a client/agent machine, the following errors occur:

 

D:\Program Files (x86)\CA\Workload Automation AE>autoping -m <machine_name> 

CAUAJM_E_10527 Timed out waiting for response from the CA WAAE Application Server: [<AutoServer>:<AutoServerPort>] 

CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s). 

 

Question:

Why doesn't autoping work on the client/agent machine but works on the Scheduler? The cryptkey.txt file is the same on both agent machine and the client/agent machine.

 

Answer:

If the client/agent port is open bidirectionally, the connection is successful via telnet and the cryptkey.txt files included in the agent directories are the same, then follow these steps:

1.- Locate the config.$AUTOSERV files (or config.%AUTOSERV% files) from client/agent machine and scheduler.

2.- Within the files, search for the 'UseEncryption' parameter and make sure they match.

3.- Go to the scheduler and get the cryptkey.txt located in the $AUTOUSER path (on Linux/UNIX) or %AUTOUSER% path (on Windows) and copy this file over to the problematic client/agent machine under the same path.

4.- Restart the services on the problem machine and try to autoping the agent again

Environment

Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option
Component: