RA FTP agent not starting as seen in AWI /Service manager dialog
Can see below errors in agent logs
U02000159 Initiate reconnect to the AE system.
U02000072 Connection to system 'SYSTEM' initiated.
U02000011 Connection to Server 'server:port' initiated.
U02000251 Timeout while reading the CP info.
Failed to connect to any CP
U02000196 Next attempt to create a CP connection in '600' seconds.
U02000041 Shutdown Agent '[AGENT_NAME]'.
agentStopped: [AGENT_NAME]
U02000001 Agent '[AGENT_NAME]' version '12.2.2' ended normally.
U02000126 There is no connection to the Server, message 'EXSTOP' cannot be sent.
Errors in Service manager agent logs
U00022008 Could not start process 'UC4 AGENT NAME'. Error Code '2'.
The system cannot find the file specified
U00022019 Client statement: process 'UC4 AGENT NAME' should be started.
U00022031 Client data: User '0/UC/UC' of computer 'servername'.
U00022004 Starting process 'UC4 AGENT NAME' ...
U00022005 ... with command line 'C:\Program Files\Java\jre1.8.0_202\bin\java -jar -Xmx2048M -Klog4j2.formatMsgNoLookups=true C:\Automic\ServiceManager\bin\..\..\'.
U00022006 ... and start directory 'C:\Automic\ServiceManager\bin\..\..\Agents\ra_ftp\bin'.
U00022008 Could not start process 'UC4 AGENT NAME'. Error Code '2'.
The system cannot find the file specified
U00022019 Client statement: process 'UC4 AGENT NAME' should be started.
U00022031 Client data: User '0/UC/UC' of computer 'servername'.
U00022004 Starting process 'UC4 AGENT NAME' ...
U00022005 ... with command line 'C:\Program Files\Java\jre1.8.0_202\bin\java -jar -Xmx2048M -Klog4j2.formatMsgNoLookups=true C:\Automic\ServiceManager\bin\..\..\'.
U00022006 ... and start directory 'C:\Automic\ServiceManager\bin\..\..\Agents\ra_ftp\bin'.
U00022008 Could not start process 'UC4 AGENT NAME'. Error Code '2'.
The system cannot find the file specified
Release : 12.3
Component :RA FTP agent
It was observed the java version used by the RA FTP agent got upgraded and the agent was not able to find the correct agent executable path as defined in service manager
Reinstalled original java version and path on server which the agent was using previously after which the agent started back successfully