HM 8.28 on W2003 as a service
We had some short network disruptions after which all perfmon tests except "CPU" on all servers stay on "checking" and have timeouts. There is no more hint that the servers aren't running well.
And clicking on the "get current value"-button in the Edit test properties dialogue you get the current value of the perfmon test.
Any idea? (server already restarted)
Thomas
PerfMon tests stay on "checking"
-
thomasschmeidl
- Posts: 166
- Joined: Sat Apr 15, 2006 2:14 pm
- Location: Germany, Bavaria
-
KS-Soft Europe
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
I assume, you are using RCC.
When you click "Get current value" button, RCC by itself connects to the target host (also it can be local host) and retrieves value.
While HostMonitor can`t do that.
Please check the following:
1) you are using account with admin rights for these tests
2) RPC service is started on both systems (system where HostMonitor is running and target host)
3) Remote Registry service should be started on target system as well
4) Check if account that you are using for the test has KEY_READ access to the following registry key on target system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib.
To view/change permissions to the registry key you can use the registry editor utility (Regedt32.exe).
5) no firewall between 2 system blocks TCP ports above 1023
6) perfOS.DLL should be enabled on target system
Microsoft provides "Extensible Counter List" utility.
This utility displays list of DLLs that are used to support Performance Counters, using the utility you may disable/enable specific DLLs.
When you click "Get current value" button, RCC by itself connects to the target host (also it can be local host) and retrieves value.
While HostMonitor can`t do that.
Please check the following:
1) you are using account with admin rights for these tests
2) RPC service is started on both systems (system where HostMonitor is running and target host)
3) Remote Registry service should be started on target system as well
4) Check if account that you are using for the test has KEY_READ access to the following registry key on target system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib.
To view/change permissions to the registry key you can use the registry editor utility (Regedt32.exe).
5) no firewall between 2 system blocks TCP ports above 1023
6) perfOS.DLL should be enabled on target system
Microsoft provides "Extensible Counter List" utility.
This utility displays list of DLLs that are used to support Performance Counters, using the utility you may disable/enable specific DLLs.
Quote from the manual
===============
Note #2 (bugs): Windows implementation of performance counters has bugs. E.g., Windows 2000 (Professional, Server, and Advanced Server editions) can produce memory leak in PDH.DLL when user (application) querying performance counter that does not exist. This bug fixed in SP2. Also PDH.DLL does not work correctly with multithread applications.
That's why in HostMonitor we have implemented several different methods to work with pdh.dll:
- MultiThread - allows to start several tests in separate threads (fastest method)
- OneByOne - HostMonitor starts Performance Counter tests one by one
- Smart - multithreading model, HostMonitor tries to reload pdh.dll when error occurs
- External - HostMonitor uses external (perfobj.exe) utility to perform the tests. This is fast and most reliable method.
You can select mode using options located on Miscellaneous page in the Options dialog.
===============
That's why I would recommend to use WMI test method instead of Performance Counter.
If you have a lot of such tests and you do not have time to replace them with WMI tests, I would recommend to setup HostMonitor (or RMA if these tests performed by Remote Monitoring Agent) to use External mode.
Regards
Alex
===============
Note #2 (bugs): Windows implementation of performance counters has bugs. E.g., Windows 2000 (Professional, Server, and Advanced Server editions) can produce memory leak in PDH.DLL when user (application) querying performance counter that does not exist. This bug fixed in SP2. Also PDH.DLL does not work correctly with multithread applications.
That's why in HostMonitor we have implemented several different methods to work with pdh.dll:
- MultiThread - allows to start several tests in separate threads (fastest method)
- OneByOne - HostMonitor starts Performance Counter tests one by one
- Smart - multithreading model, HostMonitor tries to reload pdh.dll when error occurs
- External - HostMonitor uses external (perfobj.exe) utility to perform the tests. This is fast and most reliable method.
You can select mode using options located on Miscellaneous page in the Options dialog.
===============
That's why I would recommend to use WMI test method instead of Performance Counter.
If you have a lot of such tests and you do not have time to replace them with WMI tests, I would recommend to setup HostMonitor (or RMA if these tests performed by Remote Monitoring Agent) to use External mode.
Regards
Alex
-
thomasschmeidl
- Posts: 166
- Joined: Sat Apr 15, 2006 2:14 pm
- Location: Germany, Bavaria
