Within the last 6 months, we've had one of our Hostmon servers do the following twice:
1) System crashes/becomes unresponsive
2) Upon restart, resumes service
3) Shortly afterwards, we discover that the HML test profile it's using is old (anywhere from a few weeks to a few months)
4) We revert to a backup HML profile
Both times, the eventlog isn't terribly exciting, but it does have this:
The description for Event ID ( 1002 ) 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. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error detected in HML file. Invalid TopView parameters will be corrected..
Also interesting, is that when Hostmon starts up after the crash, the 'root' folder has anywhere from a few dozen to a few hundred 'blank' ping tests. The issue seems to be that somehow the HML file is getting corrupted; specifically, it seems to only have issues with semi-new updates to the HML. All the old monitors seem OK, but anything within the last few months seems at risk. Any advice on troubleshooting this ? I can supply the corrupted HML files if it helps. That said, is there an HML viewer of some kind that I can use to see if there is something odd on this tests ?
Hostmon HML file gets corrupted/reverts sporadically
-
doofologist
- Posts: 15
- Joined: Thu Mar 05, 2009 5:50 pm
What version of HostMonitor do you use?
Not sure I understand how HostMonitor can get old HML file.
Probably you do not save changes you make? You may save changes manually using menu File->Save or setup HostMonitor to save changes automatically using "Auto save" options located on Preferences page in the Options dialog.
Another note: Windows Vista, Windows 2008 and Windows 7 may pretend to write file to specified location. But when you go to look for those files, you won't find them! Windows Vista+ may store files in a "Virtual Store" under the AppData\ in your user folder.
This may confuse and lead to some problem when you are using old version of HostMonitor.
Also I would recommend to check your hard drive for errors.
Regards
Alex
Not sure I understand how HostMonitor can get old HML file.
Probably you do not save changes you make? You may save changes manually using menu File->Save or setup HostMonitor to save changes automatically using "Auto save" options located on Preferences page in the Options dialog.
Another note: Windows Vista, Windows 2008 and Windows 7 may pretend to write file to specified location. But when you go to look for those files, you won't find them! Windows Vista+ may store files in a "Virtual Store" under the AppData\ in your user folder.
This may confuse and lead to some problem when you are using old version of HostMonitor.
Also I would recommend to check your hard drive for errors.
HostMonitor is HML viewer, it shows all folders, tests, views - everything.That said, is there an HML viewer of some kind that I can use to see if there is something odd on this tests ?
Regards
Alex
-
doofologist
- Posts: 15
- Joined: Thu Mar 05, 2009 5:50 pm
We use Hostmon 8.32
The system is running on Windows 2k3, which I don't believe has Virtual Store/UAC (which is almost unfortunate, as the behavior I'm seeing would be answered nicely by that) I'm checking the HD for errors now, and we'll see what that might turn up.
I think my verbiage is wrong; it isn't finding old profiles, however it certainly appears that way. It appears that it is loading the main profile (the only one in the folder), but in these particular cases can't read many of the alerts, and instead creates the blank/generic tests in the 'root' to compensate somehow.
The system is running on Windows 2k3, which I don't believe has Virtual Store/UAC (which is almost unfortunate, as the behavior I'm seeing would be answered nicely by that) I'm checking the HD for errors now, and we'll see what that might turn up.
I think my verbiage is wrong; it isn't finding old profiles, however it certainly appears that way. It appears that it is loading the main profile (the only one in the folder), but in these particular cases can't read many of the alerts, and instead creates the blank/generic tests in the 'root' to compensate somehow.