Error: The remote procedure call failed
Error: The remote procedure call failed
OS: Windows 2000 Server
HM: 5.82 Beta (tested with 5.66 as well)
Test Method: Performance Counter
Check Counter: \\SERVERNAME\Memory\Available MBytes
Problem: it works with some servers and with some not. There is no relation between them. Some are in the same LAN, some not. Some are the same hardware, some not. Some are on the same domain, some not. Sometimes we redo the configuration and it starts working again and it breaks after some time.
What can we do to fix this?
HM: 5.82 Beta (tested with 5.66 as well)
Test Method: Performance Counter
Check Counter: \\SERVERNAME\Memory\Available MBytes
Problem: it works with some servers and with some not. There is no relation between them. Some are in the same LAN, some not. Some are the same hardware, some not. Some are on the same domain, some not. Sometimes we redo the configuration and it starts working again and it breaks after some time.
What can we do to fix this?
You may find many articles related to Performance Counter problems in this forum. Please use Search function
Sometimes its simple configuration issue (e.g. Remote Registry service is not started on remote system). But often problems caused by various bugs in Performance Counter implementation, IMHO its the worst part of the Windows.
That's why we have implemented WMI test method in version 5.82, it works much more releable and can provide even more information.
http://www.ks-soft.net/hostmon.eng/rma-win/index.htm
Regards
Alex
Sometimes its simple configuration issue (e.g. Remote Registry service is not started on remote system). But often problems caused by various bugs in Performance Counter implementation, IMHO its the worst part of the Windows.
That's why we have implemented WMI test method in version 5.82, it works much more releable and can provide even more information.
If you want to monitor remote networks, we recommend to install RMASome are in the same LAN, some not. Some are the same hardware, some not. Some are on the same domain, some not.
http://www.ks-soft.net/hostmon.eng/rma-win/index.htm
Regards
Alex
"Test button" and "test item" use exactly the same code to perform the test. I assume test fails when HostMonitor tries to perform several tests at the same time. Am I right?
Some version of pdh.dll have such problem. What Service Pack have you installed?
I would recomment to use "One by one" or "External" test mode (see Misc page in the Options dialog), usually it helps
Regards
Alex
Some version of pdh.dll have such problem. What Service Pack have you installed?
I would recomment to use "One by one" or "External" test mode (see Misc page in the Options dialog), usually it helps
Regards
Alex
SP4 with Update Roll up Package and last updates (last Tuesday).
I prefer to go the WMI way as testing one by one would delay the testings or I'm wrong?
About WMI, the memory query I'm trying is:
select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
and it seems to work, but only if the server is in the same domain. If not I get an access denied. How can I overcome this?
I prefer to go the WMI way as testing one by one would delay the testings or I'm wrong?
About WMI, the memory query I'm trying is:
select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
and it seems to work, but only if the server is in the same domain. If not I get an access denied. How can I overcome this?
Host: daemon.sif.com.arKS-Soft wrote:May I see your test settings?
Regards
Alex
Name space: root\cimv2
Query: select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
Alert if: any AvailableMBytes is < than 256
Treat unknown status as bad disabled
About the trust relationship, is not possible/desirable and some are servers without a domain. Why not using this?:
http://msdn.microsoft.com/library/defau ... mputer.asp
I cannot import this into HostMonitor. However I used similar settings, it works fine.Host: daemon.sif.com.ar
Name space: root\cimv2
Query: select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
Alert if: any AvailableMBytes is < than 256
Treat unknown status as bad disabled
I can try to use your settings, but you should export test settings into text file. Use menu File->Export into text file
What exactly is your proposition? Specify credentials for the Remote Connection?Why not using this?:
I though you already have specified user name and password that should be used for WMI test. If not, you can do that using menu Profiles -> Connection Manager
Regards
Alex
Code: Select all
;-----------------------------------------------------------------------------
;- HostMonitor`s export/import file -
;- Generated by HostMonitor at 21/02/2006 09:42:39 -
;- Source file: C:\Program Files\HostMonitor4\HMList.hml -
;- Generation mode: Selected_Tests -
;-----------------------------------------------------------------------------
; ------- Test #01 -------
Method = WMI
;--- Common properties ---
;DestFolder = Root\Servidores\Peru\DAEMON\
Title = DAEMON: Memory
Disabled = Yes
Comment =
RelatedURL =
ScheduleMode= Regular
Schedule =
Interval = 600
Alerts = Send Mail Servers
ReverseAlert= No
UnknownIsBad= No
UseCommonLog= Yes
PrivLogMode = Default
CommLogMode = Default
SyncCounters= Yes
SyncAlerts = No
DependsOn = list
MasterTest-Alive = DAEMON: Ping
;--- Test specific properties ---
Host = daemon.sif.com.ar
NameSpace = root\cimv2
Query = select AvailableMBytes from Win32_PerfRawData_PerfOS_Memory
SumMode = any ...
CompareMode = LessThan
CompareVal = 256
NoResStatus = Unknown
;-----------------------------------------------------------------------------
; Exported 1 tests
H'm... problem is:
Microsoft manuals declares Win32_PerfRawData_PerfOS_Memory.AvailableMBytes counter as uint64 type but in real life Windows returns OleStr type to the application (HostMonitor). That's why HostMonitor applies string compare rules to the counter.
I checked AvailableKBytes and AvailableBytes counters - strings as well
May be we can implement some conversion options in future versions of HostMonitor...
Regards
Alex
Microsoft manuals declares Win32_PerfRawData_PerfOS_Memory.AvailableMBytes counter as uint64 type but in real life Windows returns OleStr type to the application (HostMonitor). That's why HostMonitor applies string compare rules to the counter.
I checked AvailableKBytes and AvailableBytes counters - strings as well

May be we can implement some conversion options in future versions of HostMonitor...
Regards
Alex
Well, one by one doesn't. And about external, it says the file is missing, but I'm administering from RCC Console. Is that a bug on the console because it's checking the local system that has not the full installation? The file is in the server installation directory but after this option was checked all performance counter tests failed.