Agent fails to start and displays "not authorized to make connection" error
Article ID: 87532
CA Automic Applications Manager (AM)
When starting a Remote Agent for the first time, the Agent fails to connect to the RMI, awapi times out. Agent logs report the following error:
ErrorMsg: AwE-5126 Agent validation error
Details: AGENTNAME AGENTHOSTNAME/220.127.116.11 50000
Agent validation error : AGENTNAME AGENTHOSTNAME/18.104.22.168 50000 : java.net.ConnectException: not authorized to make connection
This error is triggered by one of the following:
- The Agent name defined during installation does not match what is listed for the Agent's object definition.
- The IP/Host detected for the Agent does not match the IP/Host listed for the Agent's object definition.
- The OS User starting the Agent does not match the Os User listed for the Agent's object definition.
- Applications Manager's environment file ($AW_HOME/site/sosite) has not been called before attempting to start the Agent.
Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Make sure the Agent name, IP/Host, and OS user parameter on the remote agent matches what is listed for the Agent's object definition as defined in the Java Web Client.
Also, make sure Applications Manager's environment file has been called before starting the Agent.