I am running Windows 2000 and HostMonitor 3.68. HostMonitor is configured to run as a service using a local system account that has full permissions for the HostMonitor program folder and it's children. When I try to stop the HostMonitor Service the following message is received:
"Could not stop the Advanced HostMonitor service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error."
Additionally, the following is logged in the Application Event Log:
"The description for Event ID ( 0 ) in Source ( HostMonService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Service failed on stop: Unable to write to hostmon.INI."
Also, I do not have an icon in the task bar for HostMonitor while it is running as a service using a specific user. However, when running as system it does. Is this normal?
Unable to shutdown HostMonitor Service
>Also, I do not have an icon in the task bar for HostMonitor while it is running as a service using a specific user. However, when running as system it does. Is this normal?
Yes, of course. Only service that uses "local system" account has rights to interract with desktop. You should assign user account using HostMonitor's settings (Service page in the Options dialog).
Quote from the manual:
--------------------
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.
--------------------
>Service failed on stop: Unable to write to hostmon.INI."
This is reason why you cannot stop service. We need to figure out why HostMonitor cannot write to hostmon.ini file. You said "account that has full permissions for the HostMonitor program folder and it's children". May be hostmon.ini has "read only" file attribute? Or may be it has different security context than folder? Can you modify and save options when HostMonitor started as application?
Regards
Alex
<font size=-1>[ This Message was edited by: KS-Soft on 2003-06-12 13:28 ]</font>
Yes, of course. Only service that uses "local system" account has rights to interract with desktop. You should assign user account using HostMonitor's settings (Service page in the Options dialog).
Quote from the manual:
--------------------
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.
--------------------
>Service failed on stop: Unable to write to hostmon.INI."
This is reason why you cannot stop service. We need to figure out why HostMonitor cannot write to hostmon.ini file. You said "account that has full permissions for the HostMonitor program folder and it's children". May be hostmon.ini has "read only" file attribute? Or may be it has different security context than folder? Can you modify and save options when HostMonitor started as application?
Regards
Alex
<font size=-1>[ This Message was edited by: KS-Soft on 2003-06-12 13:28 ]</font>