Error: The remote procedure call failed

[KS-Soft]

Well, one by one doesn't.

Could you please be more specific? What exactly means "doesn't"?
Test still returns the same "The remote procedure call failed" error? Then I assume problem relates to remote system, not to local pdh.dll. What exactly is wrong? We don't know Try to ask Microsoft.

And about external, it says the file is missing

Does it say what file is missing? perfobj.exe? This file should be located in HostMonitor's directory. RCC needs this file only if you want to click on "Get current value" button in Test Properties dialog.

Regards
Alex

[SIF]

Well, one by one doesn't.

Could you please be more specific? What exactly means "doesn't"?
Test still returns the same "The remote procedure call failed" error? Then I assume problem relates to remote system, not to local pdh.dll. What exactly is wrong? We don't know Try to ask Microsoft.

What should I say to Microsoft when the application that gives that error fixes itself by recreating the test?
Do you think they will take my request seriously?

And about external, it says the file is missing

Does it say what file is missing? perfobj.exe? This file should be located in HostMonitor's directory. RCC needs this file only if you want to click on "Get current value" button in Test Properties dialog.

Regards
Alex

When I click the external option in options window (RCC Console) a dialog is presented with the following text: "Warning: PERFOBJ.EXE module not found!". No I didn't even have the opportunity to go to any test to check if it works.

[KS-Soft]

When I click the external option in options window (RCC Console) a dialog is presented with the following text: "Warning: PERFOBJ.EXE module not found!". No I didn't even have the opportunity to go to any test to check if it works.

Warning means "Warning", its not "Error". If you click "Save" RCC will accept the option and test will be performed by external utility.

What should I say to Microsoft when the application that gives that error fixes itself by recreating the test?

You may ask why Windows sometimes returns "The remote procedure call failed" error (error returned by PdhOpenQuery or PdhCollectQueryData Windows API).

Do you think they will take my request seriously?

Interesting logic
Over 50% of posts in this forum relates to Windows problems, not HostMonitor problems. Why we are taking your questions seriously and provide as much support as we can? Why? We don't have to answer to Windows related questions, its not our product. But we do answer any questions we can.
Truth to say we know about Windows as much as you do. We can read the same manuals and technical articles you can. Unfortunately we don't know much about inside code of the Windows.
If you ask about HostMonitor, I can answer any question. But we don't know everything about Windows.

Regards
Alex

[SIF]

I think I'm asking about HostMonitor when I say that regenerating the test fixes the issue for a while. If I don't regenerate it it doesn't work at all after it failed. And the fact that if I click the button to check it now in the settings works... I doubt that's Windows to blame, maybe the first error but such problem can't be attributed to Windows IMO.

I'm thankful for the support anyway. But maybe instead of continuously blaming Microsoft you can tell us ways to fix this issues like the one of the WMI test (that seems to be troublesome as well for HM).

[KS-Soft]

I think I'm asking about HostMonitor when I say that regenerating the test fixes the issue for a while. If I don't regenerate it it doesn't work at all after it failed.

Regenerating? Do you mean you create new test item with exactly the same settings and it works? While old test item does not? If you click "Refresh" button, new test works, the old one still shows error? Unbelievably. Could you send screen shot?

But maybe instead of continuously blaming Microsoft you can tell us ways to fix this issues like the one of the WMI test (that seems to be troublesome as well for HM).

Continuously blaming Microsoft? 80% of my working time - working on Windows bugs. Its not because there are so many bugs in Windows, just because its much much more difficult to find solution to 3rd party bugs, than fix our own bugs. However I refer our customers to Microsoft support very rarely, so you cannot say I am continuously blaming Microsoft.
I never said Windows file system is buggy, or winsock leads to problems. But Performance Counter implementation is worst part of the system. Ask Microsoft.

Regarding WMI. We already modified our code to compare numbers using numeric comparison rules even if Windows says it is string. Testing...
But again, its not a bug (at least not our bug).

Regards
Alex

[SIF]

I think I'm asking about HostMonitor when I say that regenerating the test fixes the issue for a while. If I don't regenerate it it doesn't work at all after it failed.

Regenerating? Do you mean you create new test item with exactly the same settings and it works? While old test item does not? If you click "Refresh" button, new test works, the old one still shows error? Unbelievably. Could you send screen shot?

Yes, that's what I mean. When I have the issue again I will take a screenshot. But most tests were converted to WMI and I'm going on vacations so that might be in a while.

[KS-Soft]

WMI test modified.
Update available at www.ks-soft.net/download/hm587.zip

Regards
Alex

[SIF]

It works. Thanks!