What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

Remote Procedure Call error




Occassionally get a "800706BF: The remote procedure call failed and did not execute" on some of our WMI sensors. The scanning interval on all of our WMI sensors is 60 seconds or 5 minutes. Fortunately these errors seem to correct themselves within 10 seconds of the warning, but why does this happen?

The WMI Interval on the probe shows 0% even during the times we see these warnings. And open requests is less than 5, typically 0 though.

rpc sensor wmi

Created on Aug 30, 2010 2:07:05 PM

1 Reply




that would be something to investigate in the target Windows' DCOM-System or maybe the WMI Subsystem, the error however is not happening within PRTG. Which uses the same queries all the time, and from time to time the query suddenly fails on the target. Unfortunately we do not know why, it probably is the same with some WMI Counters delivering senseless values from time to time (negative CPU loads for example). If we see such problems we try to implement an "Alternative Query" for the sensor (available in the sensors "Settings"-tab), but that is not always possible.

Best Regards.

Created on Aug 30, 2010 2:17:45 PM by  Torsten Lindner [Paessler Support]

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.