Some of my WMI sensors in PRTG are down. The displayed error messages do NOT begin with an error code in the format 800xxxxx, but have (code: PExxx) appended . What can I do?
PRTG WMI error messages
The following errors that do not show the usual 800xxxxx error codes are caused by erroneous behavior of the Windows WMI sub-system either on the target or the probe system affecting the processing of the monitoring data. Another reason for experiencing PRTG specific error messages is the use of improper WQL statements in WMI Custom Sensors.
For an overview of all PE coded errors see also our list of PE codes
WMI timeout errors
Connection could not be established (code: PE015)
This is not a timeout error per se, it means that probe computer and target system weren't able to establish a WMI communication at all. Please read more about that in this article:
Request timed out (code: PE014)
The request sent to WMI takes a lot of time to be processed (by default more than 1.5x the scanning interval). It’s a recoverable error and can be countered by either increasing the scanning interval or specifying more limiting parameters for the WMI specific request (if applicable). This is directly controlled by the WMI timeout setting in the WMI Compatibility options (available in the device settings) and set to 1.5x the scanning interval if left empty or the specified amount in seconds. You might want to check the WMI timeout settings of the parent objects if several sensors run into this error.
WMI connection timed out (code: PE054) - ("WMI request timed out" in earlier versions)
PRTG’s probe didn’t succeed in sending the request to the WMI sub-system. (Timeout occurred while establishing a connection to WMI). This can be a temporary problem which can resolve itself. However, it also can mean that the probe or/and the target system needs a restart if the problem persists.
Sensor stopped due to WMI lockup. Can be restarted with pause and resume (code: PE055)
This means that PRTGs probe was able to send a request to the WMI subsystem but it didn’t return _at all_ which is about the worst thing that can happen. This error will be shown after five fails, so it is sure to assume the respective sensor is unusable and all WMI requests to that host are put on hold. Should the problem persist after a reboot of the target machine please reboot the probe computer. If this error continues to occur please consider installing a remote probe on the target computer.
WMI request timed out. Probe's WMI system had to be stopped. Please pause or delete sensor and restart probe! (code: PE051)
This is only an interim message which leads to Sensor stopped due to WMI lockup above.
Sensor could not establish a WMI connection for more than 3 successive intervals. (code: PE263)
Please see this article for details and workaround:
WMI counter value related errors
Device sends inconsistent counter data... (code: PE041)
When the Windows WMI sub-system sends data to PRTG at least two consecutive times that leads to impossible results, such as unrealistic percent values, PRTG reports this fact as “inconsistent” and puts the sensor into an error state. Should the next data be ok again, the sensor goes up again. There's no way to change that behavior because the error is caused by WMI, not by PRTG. If this keeps on happening try to use the sensor’s “Alternative Query” in the WMI Compatibility options, if available.
Device sends 64 bit counters as 32 bit values (code: PE040)
Too many 32 bit overflows (code: PE042)
PRTG relies upon many counters being 64 bit as it is taking a considerable amount of time until these counters are full and have to start counting from 0 again (which is called “overflow”). However, sometimes WMI (falsely, dependant on patch levels) uses only 32 bit for these counters, starting from 0 much more often than it should and PRTG reports this fact as “too many 32 bit overflows” or “Device sends 64 bit counters as 32 bit values”.
One way to adapt to this is to decrease the scanning interval, as this measure lowers the probability that an overflow occurs during the interval. Another way would be to use the sensor’s “Alternative Query” in the WMI Compatibility options, if available.
Invalid data (code: PE025)
One of the WMI counters this sensor uses returned a value that prevents PRTG from calculating the correct result e.g, a negative value when only positive ones are expected or a 0 for a denominator. If this error is persistent we recommend to reboot the target system.
Invalid previous data samples (code: PE026)
Some of the WMI sensors need their previous data for calculating their correct results. So when WMI sent unusable values during the scan before you'll see this message. This should be very sporadic - if it's not we recommend that you reboot the target system.
The host's WMI system returned an invalid value for Total Memory: XXX (code: PE061)
PRTG needs the total Memory in order to calculate the percentage of free memory, but WMI doesn't deliver a valid value (usually 0). Try using the Alternative Query or refer to The Repair List for WMI problems for further suggestions.
System based errors
Network card not found (code: PE043)
WMI Network sensor only. The WMI query for network traffic knows only one way to identify a network adapter: by its name. Unfortunately this name is altered by Windows now and then. At the moment the only thing you can do is to create a new sensor with the new name.
Process not found (code: PE009)
WMI Process sensor only. This means that either the process name wasn't specified correctly in the sensor settings or the process isn't running on the target machine.
WMI Exchange specific
No result set (code: PE016)
The WMI query came back empty while PRTG expected a result. This indicates that there's a problem with the host's WMI system. Please refer to The Repair List for WMI problems for suggestions what to do.
WMI Custom/Custom String specific
Query returned no records (code: PE037)
WMI did not return any data at all (record count 0). Even if the class and counters exist, sometimes WMI simply does not return any data. One reason for this is an improper restriction like a WHERE that does not exist. For example, SELECT FreeMegaBytes FROM Win32_PerfFormattedData_PerfDisk_LogicalDisk WHERE Name=’Z:\’ but there is no Z: on the host computer.
No field specified in WQL (code: PE044)
The WQL query did not contain a field. We suggest that you check the syntax of the request and ensure that it contains a correct field, for example, SELECT field_name FROM class_name.
Too many fields specified in WQL (code: PE045)
The WQL query contained too many fields. Because WMI can only process one field per request, we suggest that you check your query and make sure that it follows the correct syntax exactly, for example SELECT only_one_field_name FROM class_name.
Could not parse WQL (code: PE046)
The WQL query did not contain entries for SELECT and/or FROM. Please check your query and ensure that both keywords are present in your WQL command.
Could not open WQL file (code: PE047)
The WQL file could not be opened. This is because the file with the query that is to be sent to WMI is not available on the machine where the probe is running.
Your WQL query code must be stored in a file on the system of the probe the sensor is created on. If used on a remote probe, the file must be stored on the system running the remote probe. In a cluster setup, please copy the file to every cluster node.
Query returned more than one record (code: PE078)
WMI returned too much data while PRTG expected only a single result. This means that the result contained more than one row, which indicates that the result was not properly restricted. For example, SELECT field_name FROM class_name WHERE <conditional_expression> where the <conditional_expression> is something like Name= 'C:'.
WMI Pagefile/Volume/Security Center (Antivirus) specific
Ambiguous result set (code: PE017)
WMI returned too much data while PRTG expected only a single result. This means that the result contained more than one row. Unfortunately, there is no apparent reason for this behavior.