Running as a Service
-
ronbernier
- Posts: 7
- Joined: Fri Jun 22, 2007 2:53 pm
Running as a Service
When logged in as my domain user account, a test via external program runs fine from Host Monitor ... All of my code for the external program, etc, utilizes UNCs when running, as I knew I would be converting the Host Monitor install to run as a service ... However, these same tests that work fine when logged in as me, return an "Unknown" status when running as a service that is configured with my domain username and password ... Is this a limitation, a known issue, or something I have configured incorrectly ???
-
ronbernier
- Posts: 7
- Joined: Fri Jun 22, 2007 2:53 pm
Working Now
[quote="KS-Soft"]The same account should lead to the same results. Have you specified username/password on Service page in the Options dialog (HOSTMONITOR Options dialog)?
What Windows do you use?
Service Pack?
HostMonitor version?
Do you see message like "logged on as user ..." message in system log?
Regards
Alex[/quote]
Yes, I've specified the username/password on the Service Page in the Options Dialog
Windows XP Service Pack 2 with Host Monitor 6.80
I do not see any "logged on as a user" entry in the system log ...
However, based on your question of the username/password being specified under options, I:
1> loaded Host Monitor in Application mode with the service running
2> deleted the information under the Startup tab under Options
3> closed Host Monitor in Application mode
4> loaded Host Monitor in Application mode with the service running
5> configured the information under the Startup tab under Options
6> closed Host Monitor in Application mode
7> Stopped and re-started the service, and everything appears to be functioning
What Windows do you use?
Service Pack?
HostMonitor version?
Do you see message like "logged on as user ..." message in system log?
Regards
Alex[/quote]
Yes, I've specified the username/password on the Service Page in the Options Dialog
Windows XP Service Pack 2 with Host Monitor 6.80
I do not see any "logged on as a user" entry in the system log ...
However, based on your question of the username/password being specified under options, I:
1> loaded Host Monitor in Application mode with the service running
2> deleted the information under the Startup tab under Options
3> closed Host Monitor in Application mode
4> loaded Host Monitor in Application mode with the service running
5> configured the information under the Startup tab under Options
6> closed Host Monitor in Application mode
7> Stopped and re-started the service, and everything appears to be functioning
-
ronbernier
- Posts: 7
- Joined: Fri Jun 22, 2007 2:53 pm
Continuing
It appears to still be happening ... The external program needs to send an errorlevel back to HostMonitor (running as a service), but apparently HostMonitor is not receiving the errorlevel back from the external app when ran as a service ... I'm suspecting, actually, that this is a limitation of Windows ...
If anyone has got this working, any help from the forum would be appreciated, too ...
If anyone has got this working, any help from the forum would be appreciated, too ...
-
ronbernier
- Posts: 7
- Joined: Fri Jun 22, 2007 2:53 pm
Now Working
Once again, the problem was user error on my part LOL ... In searching the forums, I came across this:
Note #1: When HostMonitor starts as a service, it uses the system account (as all interactive services). But this account may not have all the necessary permissions, so some tests will not work correctly (UNC test, "disk free space" test for shared drives, "CPU Usage" test for remote machines, etc). If you need these tests, you will need to assign a special user account on the Service page in the Options dialog. In this case HostMonitor will impersonate the security context of the user. Do not change the account using the system utility "Services". If you do so, HostMonitor may be unable to interact with the desktop.
I had the service password in the Options tab, but ALSO had it in the service config in windows ... CHanged that to SYstem, and allow it to interact with the desktop, and voila, it is working now ...
I've worked with AHM since version 3.x ... I love the product ... Every time I think of something that AHM might be able to do, eventually I get it working ... A bit of feedback I'd provide, though, is even though everything is documented, sometimes it's locating the multiple pieces from multiple areas and the (sometimes) slightly abbreviated explanations that's tough to get things working the first time ... Don't take that as a huge knock, just some constructive feedback ...
Note #1: When HostMonitor starts as a service, it uses the system account (as all interactive services). But this account may not have all the necessary permissions, so some tests will not work correctly (UNC test, "disk free space" test for shared drives, "CPU Usage" test for remote machines, etc). If you need these tests, you will need to assign a special user account on the Service page in the Options dialog. In this case HostMonitor will impersonate the security context of the user. Do not change the account using the system utility "Services". If you do so, HostMonitor may be unable to interact with the desktop.
I had the service password in the Options tab, but ALSO had it in the service config in windows ... CHanged that to SYstem, and allow it to interact with the desktop, and voila, it is working now ...
I've worked with AHM since version 3.x ... I love the product ... Every time I think of something that AHM might be able to do, eventually I get it working ... A bit of feedback I'd provide, though, is even though everything is documented, sometimes it's locating the multiple pieces from multiple areas and the (sometimes) slightly abbreviated explanations that's tough to get things working the first time ... Don't take that as a huge knock, just some constructive feedback ...
