Multiple tests on one server resulting in mixed status!

shereec · Post by **shereec** » Wed Sep 22, 2004 12:21 am

OS version - Windows 2000 Professional SP4

HostMonitor version – 4.60

Problem description – Some services on the one server have BAD status, whereas other services are OK. What could be the cause of this issue as we are using the Enterprise licence, therefore haven't run out of HostMonitor tests? I have currently disabled these tests until I find a resolution for this error.

KS-Soft · Post by **KS-Soft** » Wed Sep 22, 2004 12:21 pm

"Bad" status for service means
- service is not started
- or service does not respond to SERVICE_CONTROL_INTERROGATE command.
Please note: device drivers do not respond to SERVICE_CONTROL_INTERROGATE command

Regards
Alex

shereec · Post by **shereec** » Wed Sep 22, 2004 4:32 pm

I do already know that the services on the servers are started/working

Which is why I was asking the question.

Examples as below:
SVRNAME BackupExecAgentBrowser Bad
SVRNAME BackupExecDeviceMediaService Bad
SVRNAME BackupExecJobEngine Bad
SVRNAME BackupExecNamingService Bad
SVRNAME BackupExecRPCService Bad
SVRNAME BupExecAgentAcc Ok

Is it possible to change the interrogate command to QueryServiceStatusEx to allow these tests to work? Or another command?

Marcus · Post by **Marcus** » Thu Sep 23, 2004 8:43 am

I do already know that the services on the servers are started/working

Can you stop the services manually without errors?? Do they actually work?

We have found out more than once that when Windows states a service is running and when HostMonitor states it's not, HostMonitor is right

KS-Soft · Post by **KS-Soft** » Thu Sep 23, 2004 11:46 am

Is it possible to change the interrogate command to QueryServiceStatusEx to allow these tests to work? Or another command?

As I understand QueryServiceStatusEx retrieves information about service from Service Control Manager but it doesn't really send command to service and does not wait for responce from service.
SERVICE_CONTROL_INTERROGATE is real command that is sending to the service and then HostMonitor waits for response. I think its the most reliable method. Of course if some service does not support this command (but normally it must!), HostMonitor will report "Bad" status. But if service was properly designed, HostMonitor will detect the problem in case service is started but doesn't work correctly.

Regards
Alex