SAM - APM Service Control not starting windows services.

Question

2014-07-21 21:06:22,230 [1] INFO APMServiceControl.Program - Server & Application Monitor Service Control

2014-07-21 21:06:22,259 [1] WARN APMServiceControl.ControlServiceParams - Unable to parse component Id as an integer (${ComponentId}).
2014-07-21 21:06:22,259 [1] WARN APMServiceControl.ControlServiceParams - Unable to parse component Id as an integer (${ComponentId}).
2014-07-21 21:06:22,274 [1] WARN APMServiceControl.ControlServiceParams - Unable to parse component Id as an integer (${ComponentId}).

2014-07-22 09:13:42,668 [1] INFO APMServiceControl.Program - Server & Application Monitor Service Control

2014-07-22 09:13:42,684 [1] WARN APMServiceControl.ControlServiceParams - Unable to parse component Id as an integer (${{ComponentId}}).
2014-07-22 09:13:42,684 [1] WARN APMServiceControl.ControlServiceParams - Unable to parse component Id as an integer (${{ComponentId}}).

I tried with the single and double brackets. Neither works. The command in the Advance Alert Engine is

APM\APMServiceControl.exe ${ComponentId} -c=START

jkim1 · Accepted Answer

I found the culprit it was in the "TRIGGER CONDITION" tab. I had the change the "TYPE OF PROPERTY TO MONITOR" from "APM: Application", to "APM: Component", then adjust the conditions from Application Status equal DOWN to Component Status equal DOWN.

Also added Component Type=9 for Window Service. .... and TADA the APMSERVICECONTROL is working again.

SAM - APM Service Control not starting windows services.

Top Replies