New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


My WMI sensors show errors with a PE code. What does that mean?

Votes:

2

Your Vote:

Up

Down

Some of my WMI sensors in PRTG show a Down status. The displayed error messages do NOT begin with an error code in the format 800xxxxx, but have (code: PExxx) appended. What can I do?

error pe-code prtg troubleshooting wmi

Created on Feb 19, 2010 12:14:23 PM by  Volker Uffelmann [Paessler Support]

Last change on Aug 7, 2019 4:53:20 AM by  Maike Behnsen [Paessler Support]



1 Reply

Accepted Answer

Votes:

4

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 19 or later

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 subsystem 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 What does error code PExxx mean?


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 were not able to establish a WMI communication at all. For more details, see Why do I receive the sensor error message 'Connection could not be established (code: PE015)'?

Request timed out (code: PE014)

The request sent to WMI takes a lot of time to be processed (by default more than 1.5 times the scanning interval). It is 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.5 times the scanning interval if left empty or set to 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 system overload. Please extend the scanning intervals of your WMI sensors and/or use remote probes for load balancing. (code: PE054)

PRTG did not succeed in sending the request to the WMI subsystem. This can be a temporary problem which can resolve itself. However, it can also mean that the probe and/or the target system need a restart if the problem persists.

Sensor stopped due to WMI lockup. Can be restarted with pause and resume (code: PE055)

This means that PRTG was able to send a request to the WMI subsystem but it did not return at all. This is about the worst thing that can happen. This error will be shown after five fails, so you can assume that 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, reboot the probe computer. If this error continues to occur, consider installing a remote probe on the target computer.

WMI request timed out unrecoverably. If the problem persists with this sensor consider pausing or deleting it. (code: PE051)

This is only an interim message which leads to the error message Sensor stopped due to WMI lockup. Can be restarted with pause and resume (code: PE055) above.

Sensor could not establish a WMI connection for more than 3 successive intervals. (code: PE263)

For details and a workaround, see Why do my WMI sensors show error PE263 after updating PRTG?


WMI Counter Value-Related Errors

Device sends inconsistent counter data... (code: PE041)

When the Windows WMI subsystem sends data to PRTG for at least two consecutive times, this leads to impossible results, such as unrealistic percent values. PRTG reports this fact as “inconsistent” and sets the sensor to a Down status. Should the data sent next be ok, the sensor goes up again. There is no way to change this behavior because the error is caused by WMI, not by PRTG. If this keeps on happening, try to use the sensor’s Alternative Query option in the WMI Compatibility settings, 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 takes a considerable amount of time until these counters are full and have to start counting from 0 again (this is called overflow). However, WMI sometimes (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 (code: PE042) or Device sends 64 bit counters as 32 bit values (code: PE040).

One way to adapt to this is to decrease the scanning interval, as this measure lowers the probability that an overflow occurs during the scanning interval. Another way is to use the sensor’s Alternative Query option in the WMI Compatibility settings, 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, for example, a negative value when only positive values are expected, or a 0 for a denominator. If this error is persistent, we recommend that you 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 if WMI sent unusable values during the scan before, you will see this message. This should be very sporadic - if it is 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 to calculate the percentage of free memory, but WMI does not deliver a valid value (usually 0). Try to use he sensor’s Alternative Query option in the WMI Compatibility settings or see I have tried a lot of things to fix my WMI. What else can I try to avoid reinstalling Windows? for further suggestions.


System-Based Errors

Network card not found (code: PE043)

This only applies to the Windows Network Card sensor. 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)

This only applies to the Windows Process sensor. This means that either the process name was not correctly specified in the sensor settings or the process is not running on the target machine.


WMI Exchange-Specific Errors

No result set (code: PE016)

The WMI query came back empty while PRTG expected a result. This indicates that there is a problem with the host's WMI system. For further suggestions what to do, see I have tried a lot of things to fix my WMI. What else can I try to avoid reinstalling Windows?


More Errors

WMI Custom/Custom String-Specific Errors

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 recommend 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 recommend 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. 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, 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 Errors

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.


More

Created on Feb 19, 2010 12:55:08 PM by  Volker Uffelmann [Paessler Support]

Last change on Aug 7, 2019 5:22:14 AM by  Maike Behnsen [Paessler Support]



Please log in or register to enter your reply.


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.