ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Windows Agent not going to RUNNING status after reboot


Article ID: 88987


Updated On:


CA Automic Applications Manager (AM)


Windows Agent not going to RUNNING status after reboot


Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent


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:

10:03:13.130 HB: .MasterSocketManager: sendRequest  SeqNo 1180011 Agent UA-APS221A Master null service checkNetwork Method checkConnection
10:03:13.130 MSM:read-UA-APS221A: AwE-5103
10:03:13.130 MSM:read-UA-APS221A: .AxOptions: NoErrorMsgProperties=false
ErrorMsg: AwE-5103 network socket error (12/28/11 10:03 AM)
Details: 10fefa7[SSL_DH_anon_WITH_RC4_128_MD5: Socket[,port=1182,localport=50002]] Connection reset
 at Source)


?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 2008.