Windows Agent not going to RUNNING status after reboot.
Detailed Description and Symptoms
After unscheduled reboot of a Windows Remote Agent machine the RA did not come up automatically. It went from a RUNNING to SRVC_DOWN status on the Applications Manager GUI.
The logs on the Masters RmiServer##.log show the following:
HB: .MasterSocketManager: sendRequest Master null service checkNetwork Method checkConnection
ErrorMsg: AwE-5103 network socket error
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
Release: CA Automic Applications Manager
This appears to occur mainly during unscheduled restarts and will be seen mostly on test machines shared across applications that are frequently rebooted without stopping services.
To fix the issue at the time it occurs the Agents Service needs to be stopped/restarted.
A long term solution may be to use the 'Delayed Start' option for the AM service on Windows.