PRTG stopped talking to 6 servers this morning citing WMI connection could not be established. I'll buy 1 server having a WMI issue, but 6 all at once? Not even in this environment do I agree with that. This is clearly a PRTG problem that needs to be addressed.
WMI
Modified on 2025-06-10 13:48:56 +0200
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
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.
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.
It's likely that your probe machine's WMI is having the problems as WMI is very unreliable the more you try to monitor with it and the rate at which you request updates. If you check the probe health sensor you can see if its experiencing poor WMI performance.
If you can post the error message you get from PRTG that would be helpful too, or any from the eventlogs.
Apr, 2014 - Permalink