I noticed SERVICE_CONTROL_INTERROGATE errors in CA Workload Automation System Agent logs on Windows hosts. Example: Tue Sep 20 17:02:00 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE What are these messages for?

Document ID : KB000011692
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

I noticed SERVICE_CONTROL_INTERROGATE errors in CA Workload Automation System Agent logs on Windows hosts.

Example: The runner_os_component.log file contained the following messages

Tue Sep 20 17:02:00 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE
Tue Sep 20 17:07:09 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE
Tue Sep 20 17:12:18 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE
Tue Sep 20 17:17:27 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE
Tue Sep 20 17:22:36 2016: ServiceControl called with SERVICE_CONTROL_INTERROGATE

What are these errors suggesting?

Environment:
CA Workload Automation Agent 11.3.x on MS Windows systems.
Answer:

The 'ServiceControl called with SERVICE_CONTROL_INTERROGATE' message is just informational in the normal Windows service processing code. It is not an error. The code loop that is writing this message is the Service Handler that gets called to pause, continue, stop/shutdown, or interrogate the service. These messages are logged when something has started to notify the CA WA System Agent service that it should report its status information to the Windows Service Control Manager (SCM). The parameter for the interrogation request is SERVICE_CONTROL_INTERROGATE and the Windows documentation states that all services must accept and process the SERVICE_CONTROL_INTERROGATE control code.

 

Additional Information: