We are running Hostmonitor v9.58 on Windows Server 2008 R2 as a Windows Service.
When changing tests we connect via the Remote Connect Console. Changes appear to be saved but when the Windows service is restarted the changes are lost.
Restarting the service gives some problems though. He hangs on "Stopping service..." forcing us to kill the process. Which may be the cause that we lose our changes...
Restarting the service by rebooting the server has the same effect.
Do we miss some kind of configuration? Will the fact that we need to kill the process be the cause of our changes not being saved?
Thanks for your feedback!
Running as Windows Service, changes via RCC are not saved
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
If HostMonitor process is terminated by killing the process, all unsaved data will be lost.
You may save data manually using menu File -> Save
Also, you may setup autosave option using menu Options -> Preferences
Note1: If you have large amount of test items, it's not recommended to use "Auto save TestList after any changes" option. This option may slow down HostMonitor performance.
Note2: You may use HMS script command "SaveTestList" and start HMS script on regular basis.
You may save data manually using menu File -> Save
Also, you may setup autosave option using menu Options -> Preferences
Note1: If you have large amount of test items, it's not recommended to use "Auto save TestList after any changes" option. This option may slow down HostMonitor performance.
Note2: You may use HMS script command "SaveTestList" and start HMS script on regular basis.
The data was saved by the auto-save function before the process was killed.
A manual save was no longer possible (grayed out), probably because of the auto-save.
But if the process is being killed after the testlist was saved, the changes should not be lost I suppose?
Any idea what may be the reason our changes are no longer visible after the Windows service is restarted?
A manual save was no longer possible (grayed out), probably because of the auto-save.
But if the process is being killed after the testlist was saved, the changes should not be lost I suppose?
Any idea what may be the reason our changes are no longer visible after the Windows service is restarted?
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Correct.But if the process is being killed after the testlist was saved, the changes should not be lost I suppose?
What exactly settings are lost? Test settings? Some global options, like log settings?
Have you checked system log (RCC menu View -> Auditing tool... -> Recent syslog)?
UAC enabled?
What user account is specified on Service page of Options dialog?
It is recommended to specify BUILT-IN Administrator account on Service page of Options dialog on UAC enabled systems.
Looks like we found the problem.
In het windows services mmc the hostmonitor was running under a custom service account 'srv_hostmonitor' but in the hostmonitor settings under startup/service/log on as was set to "local system account".
We changed it to use account "srv_hostmonitor" and the service restarted perfectly now without any loss of changes.
One small problem remains, when we restart the service and connect with the rcc , the monitoring is not started. I can manually start the monitoring with the rcc , but after restart the service the monitoring is again stopped.
We checked the hostmonitor startup settings and it was set to "start after loading" , we tried changing it to "restore last status", but the hostmonitor is never running after restarting the service.
Is this normal or did we do something wrong ?
In het windows services mmc the hostmonitor was running under a custom service account 'srv_hostmonitor' but in the hostmonitor settings under startup/service/log on as was set to "local system account".
We changed it to use account "srv_hostmonitor" and the service restarted perfectly now without any loss of changes.
One small problem remains, when we restart the service and connect with the rcc , the monitoring is not started. I can manually start the monitoring with the rcc , but after restart the service the monitoring is again stopped.
We checked the hostmonitor startup settings and it was set to "start after loading" , we tried changing it to "restore last status", but the hostmonitor is never running after restarting the service.
Is this normal or did we do something wrong ?