Hello !
I have some problems after applying W2k Sp4 and the RPC-fix on all my servers.
I monitor w2k servers in my domain, so no extra user/password is necessary.
The performance counter values aren't available on the servers from time to time.
Sometimes I can monitor all servers and sometimes a handfull of servers in unavailable ?
Have you got any ideas ?
Regards
Sven
Problems after RPC fix
So, problem appears after you installed RPC patch..
What PerfWorkMode do you use?
http://www.ks-soft.net/hostmon.eng/mfra ... #perfnotes
-----------------------------------
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 mode: HostMonitor works almost according to Microsoft documentation with some workaround to avoid most likely problems. HM loads pdh.dll at once and uses it all the time. This method fast because HM can start several tests simultaneously. If everything will work correctly on your system, use this method (by default HostMonitor uses this method).
OneByOne mode: Using this method HM will start Performance Counter tests one by one and reload pdh.dll every time. This method slow (when you setup Performance Counter test using Test Properties dialog program even can hang for 1-2 min) but using this method you will avoid some problems due to a buggy pdh.dll
Smart mode: With this method HM will try to detect when pdh.dll need to be reloaded.
To change mode, add line "PerfWorkMode=N" to hostmon.ini file into [Misc] section and restart HostMonitor. N is number of the mode: 0 - MultiThread mode, 1 - OneByOne mode, 2 - Smart mode
-----------------------------------
Usually "OneByOne" mode helps in similar situations.
Regards
Alex
What PerfWorkMode do you use?
http://www.ks-soft.net/hostmon.eng/mfra ... #perfnotes
-----------------------------------
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 mode: HostMonitor works almost according to Microsoft documentation with some workaround to avoid most likely problems. HM loads pdh.dll at once and uses it all the time. This method fast because HM can start several tests simultaneously. If everything will work correctly on your system, use this method (by default HostMonitor uses this method).
OneByOne mode: Using this method HM will start Performance Counter tests one by one and reload pdh.dll every time. This method slow (when you setup Performance Counter test using Test Properties dialog program even can hang for 1-2 min) but using this method you will avoid some problems due to a buggy pdh.dll
Smart mode: With this method HM will try to detect when pdh.dll need to be reloaded.
To change mode, add line "PerfWorkMode=N" to hostmon.ini file into [Misc] section and restart HostMonitor. N is number of the mode: 0 - MultiThread mode, 1 - OneByOne mode, 2 - Smart mode
-----------------------------------
Usually "OneByOne" mode helps in similar situations.
Regards
Alex
Hello !
I updated the pdh.dll with a W2k Post SP4 hotfix from Microsoft 825882 to see if that solvewd my problem, but the problem persists, I now use PerfWorkMode=1, that is the only way I can get it to work.
A thing I noticed is: the problem often start when testing on our NT4 Citrix server, sometimes this is the only server with problems, and sometimes the problem moves on to other servers. The NT4 server is with SP6 and Security rollupfixes added.
Regards
Sven
I updated the pdh.dll with a W2k Post SP4 hotfix from Microsoft 825882 to see if that solvewd my problem, but the problem persists, I now use PerfWorkMode=1, that is the only way I can get it to work.
A thing I noticed is: the problem often start when testing on our NT4 Citrix server, sometimes this is the only server with problems, and sometimes the problem moves on to other servers. The NT4 server is with SP6 and Security rollupfixes added.
Regards
Sven