I've running hostmonitor in service mode on win2003 server.
In normal mode the test and the script works fine.
But in service mode the test stop and reply "Error: unable to start script"
When I switch in normal mode the test start run whithout error.
The script: " WScript.stdout.write "scriptres:OK:"&" TESTTEST " "
I use the test "Shell Script" to start the script.
Any ideas?
script dont work in service mode
What account you have specified on Service page in the Options dialog (HostMonitor's Options dialog)? "Local system"?
Quote from the manual
Alex
Quote from the manual
RegardsLog on as
Specify user account (login and password) to impersonate the security context of the user.
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. In this case HostMonitor will impersonate the security context of the user.
Note: Do not change the account using the system utility "Services". If you do so, HostMonitor will not be able to interact with the desktop.
Alex
I cannot reproduce this error on our Win 2003 server
Scripts works fine in application and service modes.
Could you try to execute the same command line (cmd /c cscript /B /E:VBScript anything_here) using "Execute external program" action? You may assign action to some simple test with predefined result (e.g. "good" action for "ping 127.0.0.1" test).
In this case HostMonitor will request Windows and record text information about reason of the error into syslog.htm file (or some other file specified on Advanced Logs page in the Options dialog).
Regards
Alex

Could you try to execute the same command line (cmd /c cscript /B /E:VBScript anything_here) using "Execute external program" action? You may assign action to some simple test with predefined result (e.g. "good" action for "ping 127.0.0.1" test).
In this case HostMonitor will request Windows and record text information about reason of the error into syslog.htm file (or some other file specified on Advanced Logs page in the Options dialog).
Regards
Alex