Alex:
I've decided the best and quickest way to address my memory leak issue is to completely flatten, then rebuild my Host Monitor server. (I could spend many hours simply trying to trouble shoot the problem or 1/2 day eliminating the problem.)
Of course, I want to make sure all configuration files for Host Monitor are backed up to the network so that once I re-install Host Monitor, I can restore the current config. Currently, I copy the entire directory
\Program Files\HostMonitor4 out to one of our network file servers - so I have this already.
Once the Host Monitor server is rebuilt, and Host Monitor has been re-installed, what files do I need to copy back to the server in order to restore my config?
Thanks! and oh yes, happy new year....
Backing up and restoring my config...
OK, Alex, I think I've figured this out on my own - at least it seems to be working.
I first installed Host Monitor on new machine and entered licensing info. Then I copied all .INI, .LST, and .HML files to the new installation program directory. Then I had to manually edit 2 files (HOSTMON.INI & HML_MGR.INI) because original install folder was "HostMonitor4" but new folder is "HostMonitor5"
Also, here's something interesting. The new machine and the old machine are identical boxes -- Dell PE1650s - i.e. same exact hardware. I had expected to need to copy the "version 5.7.1" of HOSTMON.EXE into the program directory to avoid the "corrupt file" at startup issue.
However, version 5.7.0 started up and ran fine - I did not need the 5.7.1 version of HOSTMON.EXE
There should be no difference between the two boxes - both have dual Pentium III procesors, same memory (2GB), same version of BIOS, same motherboards, etc. Yet, one need 5.7.1 and the other did not.
I can't explain -- but the bottom line is new machine is up and running.
I first installed Host Monitor on new machine and entered licensing info. Then I copied all .INI, .LST, and .HML files to the new installation program directory. Then I had to manually edit 2 files (HOSTMON.INI & HML_MGR.INI) because original install folder was "HostMonitor4" but new folder is "HostMonitor5"
Also, here's something interesting. The new machine and the old machine are identical boxes -- Dell PE1650s - i.e. same exact hardware. I had expected to need to copy the "version 5.7.1" of HOSTMON.EXE into the program directory to avoid the "corrupt file" at startup issue.
However, version 5.7.0 started up and ran fine - I did not need the 5.7.1 version of HOSTMON.EXE
There should be no difference between the two boxes - both have dual Pentium III procesors, same memory (2GB), same version of BIOS, same motherboards, etc. Yet, one need 5.7.1 and the other did not.
I can't explain -- but the bottom line is new machine is up and running.
If there is problem with some driver (e.g. ODBC driver) or network client, rebuild will not help.I've decided the best and quickest way to address my memory leak issue is to completely flatten, then rebuild my Host Monitor server. (I could spend many hours simply trying to trouble shoot the problem or 1/2 day eliminating the problem.)
E.g. we have report about strange resource leak on systems where both Microsoft and Novell network clients installed. If you are monitoring Microsoft resources but Novell Client is first in the Provider Order for the Network Configuration, you will see resource leakage. If you change Network Provider order, problem gone.
You may copy all *.LST, *.INI and *.HML files. You should copy all these files, then start HostMonitor. If you copy some files (not copy other) and start HostMonitor, links between profiles (e.g. action->schedule) will be lost.Once the Host Monitor server is rebuilt, and Host Monitor has been re-installed, what files do I need to copy back to the server in order to restore my config?
If you changed folder name, you may need to make more changes. E.g. path to report specific to some folder stored in HML file. This path can be changed in Folder Properties dialog only.Then I had to manually edit 2 files (HOSTMON.INI & HML_MGR.INI) because original install folder was "HostMonitor4" but new folder is "HostMonitor5"
Strange... The same CPU and manufactured date?However, version 5.7.0 started up and ran fine - I did not need the 5.7.1 version of HOSTMON.EXE
Regards
Alex
Acknowledged -- we don't run Novell here but I understand what you are saying -- i.e. Novell is just one example.KS-Soft wrote: If there is problem with some driver (e.g. ODBC driver) or network client, rebuild will not help.
E.g. we have report about strange resource leak on systems where both Microsoft and Novell network clients installed. If you are monitoring Microsoft resources but Novell Client is first in the Provider Order for the Network Configuration, you will see resource leakage. If you change Network Provider order, problem gone.
I guess we'll have to wait and see -- we have more than 40 of these particular units -- i.e. same hardware, same software/firmware and BIOS -- and this is the only host experiencing this resource problem. I should know by the end of this week wheteher or not I have to keep digging deeper.
Fortunately, we had all reporting directed to "D:\AHMReports" so I only needed to create this folder on the new box.KS-Soft wrote:If you changed folder name, you may need to make more changes. E.g. path to report specific to some folder stored in HML file. This path can be changed in Folder Properties dialog only.Then I had to manually edit 2 files (HOSTMON.INI & HML_MGR.INI) because original install folder was "HostMonitor4" but new folder is "HostMonitor5"
Yes, all these systems were originally ordered at the same time and with the same configuration, so they should be identical with resect to hardware/firmware.HoweStrange... The same CPU and manufactured date?KS-Soft wrote: ver, version 5.7.0 started up and ran fine - I did not need the 5.7.1 version of HOSTMON.EXE