autoping -m with the -S option failing on AWS Windows 2019 machine

Products

• Autosys Workload Automation

Issue/Introduction

 

Running "autoping", it worked with "-m" alone and failed when adding the -S option as displayed below:

autoping -m ########
 
 
CAUAJM_I_50023 AutoPinging Machine [########]
CAUAJM_I_50025 AutoPing WAS SUCCESSFUL.
 
autoping -m ######## -S
 
 
CAUAJM_I_50023 AutoPinging Machine [########]
CAUAJM_I_50031 Checking the Agent's connectivity to the Application Server.
CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.
CAUAJM_E_50041 ERROR: Agent returned <OpenFailure, CAUAJM_E_10032 Unable to create server object for host [########].>.
CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.
 
CAUAJM_E_50037 ERROR: Agent failed to communicate with Application Server.
CAUAJM_E_50041 ERROR: Agent returned <OpenFailure, CAUAJM_E_10032 Unable to create server object for host [########].>.
CAUAJM_E_50283 AutoPing from the Application Server WAS NOT SUCCESSFUL.
 
CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.

Similarly, when running "autorep" from the Windows host, it also failed with the following error:

C:\Program Files\CA\Workload Automation AE>autorep -w -m ALL

CAUAJM_E_00088 Could not get host information for [########].  Not started. 
CAUAJM_E_50033 Error initializing tx subsystem:  CAUAJM_E_10032 Unable to create server object for host [########].

Environment

Windows 2019

AutoSys Client 12.1.x

Resolution

To resolve the autoping with the -S option failing, an entry was added in the /etc/hosts file for the ip address and hostname of the Scheduler and Client machine.

To resolve the autorep issue, need to set the PATH environmental variable to use the %SOCKADAPTER%\bin64 directory, instead of %SOCKADAPTER%\bin directory.

Additional Information

Client deployed Autosys agent-client on AWS Windows 2019 via an MSI package.