Hi,
I've got 3.68 running as a service on a Windows NT4.0sp6a machine.
- interaction with desktop is disabled
- in "NT4" service manager, it's started with the "system account"
- in HM, I'm using a different account to do things.
Now, HM seems to start properly, the monitoring starts, syslog shows a proper startup, test-logfiles are updated properly.
All in all, HM seem to run properly.
However, in the event log i get following events :
Immediately after booting - application log :
"SERVICE STARTED"
After the 1 minute delay - application log :
"LOGGED ON AS USER 'domainuser'
Another minute or so later - system log :
"THE ADVANCED HOST MONITOR SERVICE HUNG ON STARTING"
However, as I said, everything seems to work just fine.
Any idea ???
Ludo
Incorrect service control manager message
>Immediately after booting - application log : "SERVICE STARTED"
This is the service startup
After the 1 minute delay - application log : "LOGGED ON AS USER 'domainuser'
This is the user you use for your tests. The one minute delay is set in your options dialog of HM.
Another minute or so later - system log : "THE ADVANCED HOST MONITOR SERVICE HUNG ON STARTING"
This is just windows, telling you it did not get a confirmation of HM it has started within the time out.
This is the service startup
After the 1 minute delay - application log : "LOGGED ON AS USER 'domainuser'
This is the user you use for your tests. The one minute delay is set in your options dialog of HM.
Another minute or so later - system log : "THE ADVANCED HOST MONITOR SERVICE HUNG ON STARTING"
This is just windows, telling you it did not get a confirmation of HM it has started within the time out.
Actually HostMonitor reports its running after it loaded necessary DLL's and settings (5-15 sec after start). However some systems display that "SERVICE HUNG ON STARTING" message while service works fine. Why? We don't know We never was able to reproduce this message (of course we can reproduce it by removing some HostMonitor's code, but in normal situation we don't see it).
If HostMonitor updates log files, it works. So, just ignore that message.
Regards
Alex
If HostMonitor updates log files, it works. So, just ignore that message.
Regards
Alex
In some manual I have seen information about 20 sec timeout (probably it depends on Windows version). But I don't see this message even if HostMonitor reports after 30 sec (slow down HostMonitor for testing purpose).
And what is interesting: Ludo see this message after 2 min HostMonitor is running!?
Regards
Alex
And what is interesting: Ludo see this message after 2 min HostMonitor is running!?
Regards
Alex
OK - message clear : it works - therefor : be happy don't worry. But I'm glad it's more or less explainable.
For you interests maybe I'll list the exact timings ...
16:22:54 : service started
16:23:55 : logged on as "domain/user" (I indeed set delay to 1 minute)
16:24:31 : service hung
The system (P4)is not quite so busy at that time really - there is nothing much to start.
And Alex ... it's very much reproduceable ...
Cheers,
Ludo
For you interests maybe I'll list the exact timings ...
16:22:54 : service started
16:23:55 : logged on as "domain/user" (I indeed set delay to 1 minute)
16:24:31 : service hung
The system (P4)is not quite so busy at that time really - there is nothing much to start.
And Alex ... it's very much reproduceable ...
Cheers,
Ludo