New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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


What does error code PExxx mean?

Votes:

0

Your Vote:

Up

Down

PRTG reports an error with a PE code. What does that mean?


PE001 PE002 PE003 PE004 PE005 PE006 PE007 PE008 PE009 PE010 PE011 PE012 PE013 PE014 PE015 PE016 PE017 PE018 PE019 PE020 PE021 PE022 PE023 PE024 PE025 PE026 PE027 PE028 PE029 PE030 PE031 PE032 PE033 PE034 PE035 PE036 PE037 PE038 PE039 PE040 PE041 PE042 PE043 PE044 PE045 PE046 PE047 PE048 PE049 PE050 PE051 PE052 PE053 PE054 PE055 PE056 PE057 PE058 PE059 PE060 PE061 PE062 PE063 PE064 PE065 PE066 PE067 PE068 PE069 PE070 PE071 PE072 PE073 PE074 PE075 PE076 PE077 PE078 PE079 PE080 PE081 PE082 PE083 PE084 PE085 PE086 PE087 PE088 PE089 PE090 PE091 PE092 PE093 PE094 PE095 PE096 PE097 PE098 PE099 PE100 PE101 PE102 PE103 PE104 PE105 PE106 PE107 PE108 PE109 PE110 PE111 PE112 PE113 PE114 PE115 PE116 PE117 PE118 PE119 PE120 PE121 PE122 PE123 PE124 PE125 PE126 PE127 PE128 PE129 PE130 PE131 PE132 PE133 PE134 PE135 PE136 PE137 PE138 PE139 PE140 PE141 PE142 PE143 PE144 PE145 PE146 PE147 PE148 PE149 PE150 PE151 PE152 PE153 PE154 PE155 PE156 PE157 PE158 PE159 PE160 PE161 PE162 PE163 PE164 PE165 PE166 PE167 PE168 PE169 PE170 PE171 PE172 PE173 PE174 PE175 PE176 PE177 PE178 PE179 PE180 PE181 PE182 PE183 PE184 PE185 PE186 PE187 PE188 PE189 PE190 PE191 PE192 PE193 PE194 PE195 PE196 PE197 PE198 PE199 PE200 PE201 PE202 PE203 PE204 PE205 PE206 PE207 PE208 PE209 PE210 PE211 PE212 PE213 PE214 PE215 PE216 PE217 PE218 PE219 PE220 PE221 PE222 PE223 PE224 PE225 PE226 PE227 PE228 PE229 PE230 PE231 PE232 PE233 PE234 PE235 PE236 PE240 PE241 PE242 PE243 PE244 PE245 PE246 PE247 PE248 PE249 PE250 PE251 PE252 PE253 PE254 PE255 PE256 PE257 PE258 PE259 PE260 PE261 PE262 PE263 PE264 PE265 PE266 PE267 PE268 PE269 PE270

error-code pe prtg

Created on Feb 28, 2012 2:16:08 PM by  Volker Uffelmann [Paessler Support]

Last change on May 11, 2020 9:28:52 AM by  Florian Weik [Paessler Support]



7 Replies

Accepted Answer

Votes:

2

Your Vote:

Up

Down

PE Error Codes - Overview

PE CodeMessageContext
PE001The IPs do not match. (%0:s <> %1:s)DNS IPs
PE002The DNS server does not respond. To resolve this issue, check if the DNS service on the remote host may be shut down. Also check if a firewall or IPS between the monitoring server and the remote host is sending a reject for the connection. Or tap the connection with a packet analyzing tool to see if the PRTG probe queries the correct DNS.
PE003No remote desktop service is connected. To resolve this issue, check if the RDP port is accessible.RDP (Remote Desktop) sensor; IMAP sensor
PE004No remote desktop service is running on this port.
PE005Not supported.IMAP sensor (can be used by others)
PE006The login has failed. Make sure that you entered the correct username and password.IMAP sensor
PE007Your POP3 server does not support APOP. To resolve this issue, select a different authentication type for your POP3 server.POP3 sensor
PE008The file you want to monitor cannot be found. To resolve this issue, use a file system activity monitoring tool to check if your sensor tries to access a locked or hidden file. Also check if the file exists on the computer your local or remote probe is running on. Enter the full local path. UNC paths are not allowed.WMI File sensor
PE009The Windows process you want to monitor cannot be found. To resolve this issue, check if you correctly specified the process name in the sensor settings. Also check if the process is running on the target machine.Windows Process sensor
PE010The Windows service you want to monitor cannot be found. To resolve this issue, set the sensor's scanning interval to 5 minutes or more to give the target system enough time to respond. Also make sure that the service query goes against the service name that is visible in the properties of a service.WMI Service sensor
PE011The Windows service you want to monitor is not running (%s).WMI Service sensor
PE012No DNS name
PE013The drives you want to monitor cannot be found. The reason might be that PRTG monitors the disks' DeviceIDs that can change in a cluster, for example. To resolve this issue, use a WMI Volume sensor and set it to use the drive letter for identification.WMI Free Disk Space (Multi Disk) sensor
PE014The request sent to WMI timed out. To resolve this issue, increase the sensor's scanning interval. Also specify more limiting parameters for the WMI-specific request. For more information, see https://kb.paessler.com/en/topic/1093
PE015Connection could not be establishedWMI connection
PE016The WMI query does not return any results. The reason might be an issue with the host's WMI system. For more information, see https://kb.paessler.com/en/topic/1093
PE017The WMI query returns an ambiguous result set. It returns too much data while PRTG expects only a single result. For more information, see https://kb.paessler.com/en/topic/1093WMI Custom sensor
PE018Your request has timed out. Depending on the sensor type you use, the reason might be that the sensor could not connect to the target host or that a PowerShell command takes too long to execute. For more information, see https://kb.paessler.com/en/topic/71899
or
https://kb.paessler.com/en/topic/37633
EXE/Script sensor; Windows Update Status (PowerShell) sensor; IP on DNS Blacklist sensor
PE019Could not load DLL.
PE020The content has changed.
PE021See the history for details
PE022System Error: %sEXE/Script sensors
PE023Protocol Error: %sEXE/Script sensors
PE024Content Error: %sEXE/Script sensors
PE025The sensor receives invalid data. The reason might be that one of the WMI counters that this sensor uses returned a value that prevents PRTG from calculating the correct result. To resolve this issue, restart the target system.WMI query direct
PE026The sensor received invalid previous data samples. Some WMI sensors need their previous data for calculating correct results. For more information, see https://kb.paessler.com/en/topic/1093WMI query direct
PE027The record count from the WMI query does not match the previous record count.WMI query direct
PE028UNC paths are not allowed as the name of the file you want to monitor. To resolve this issue, enter the full local path of the file. The file must exist on the computer your local or remote probe is running on.WMI File sensor
PE029Logon failure: %sSMB/File/Folder
PE030Cannot access network share: %sSMB/File/Folder
PE031Cannot access file: %sSMB/File/Folder
PE032Cannot access folder: %sSMB/File/Folder
PE033Mailbox not found: %s
PE034The sensor shows a Down status because of a simulated error. To resolve this issue, right-click the sensor and select Resume from the context menu.
PE035The request has timed out because the sensor is waiting for mutual exclusion (mutex). For more information, see https://kb.paessler.com/en/topic/57133EXE/Script sensors
PE036The sensor could not create a mutual exclusion (mutex).EXE/Script sensors
PE037The WMI/SQL query returned no records. For more information, see https://kb.paessler.com/en/topic/1093
PE038The WMI/SQL query returned more than one row. This indicates that the result was not properly restricted. For more information, see https://kb.paessler.com/en/topic/1093
PE039The connection has dropped.
PE040The device sends 64-bit counters as 32-bit values. To resolve this issue, enable an alternative query method in the WMI Alternative Query options of your sensor settings. For more information, see https://kb.paessler.com/en/topic/1093WMI processor
PE041The device sends inconsistent counter data. To resolve this issue, enable an alternative query method in the WMI Alternative Query options of your sensor settings. For more information, see https://kb.paessler.com/en/topic/1093WMI processor
PE042There are too many 32-bit overflows on the WMI counters. To resolve this issue, decrease the sensor's scanning interval. For more information, see https://kb.paessler.com/en/topic/1093WMI querydirect.process
PE043The network card cannot be found because Windows might have changed the name of the network adapter. To resolve this issue, create a new sensor with the new name.WMI network
PE044No field is specified in WQL. To resolve this issue, check the syntax of the request and make sure that it contains a correct field. For more information, see https://kb.paessler.com/en/topic/1093WMI/SQL query
PE045Too many fields are specified in WQL. To resolve this issue, check the syntax of the request and make sure that only one field per request is processed. For more information, see https://kb.paessler.com/en/topic/1093WMI/SQL query
PE046WQL could not be parsed because the WQL query did not contain entries for SELECT or FROM. To resolve this issue, check the syntax of the request and make sure that both keywords are present in the WQL command.WMI/SQL query
PE047The WQL file "%s" could not be opened. The reason might be that the file with the query is not available on the system that runs the PRTG probe. For more information, see https://kb.paessler.com/en/topic/1093
PE048The maximum trip time for an arriving email has timed out.SMTP&IMAP Round Trip sensor; SMTP&POP3 Round Trip sensor
PE049No interfaces are available on this device. To resolve this issue, check if there are any MIB files from the vendor of your device and use Paessler MIB Importer to convert the files for the SNMP Library sensor.
PE050The number of interfaces found on this device is too large. To resolve this issue, retry using a smaller .oidlib file.
PE051The WMI request has unrecoverably timed out. To resolve this issue, consider pausing or deleting the sensor. For more information, see https://kb.paessler.com/en/topic/1093
PE052Service restarted.
PE053PRTG cannot activate the server on the specified port.Syslog/SNMP Trap
PE054There has been a WMI system overload. To resolve this issue, increase the scanning intervals of your WMI sensors and/or use remote probes for load balancing.
PE055The sensor stopped because of a WMI lockup. The probe was able to send a request to the WMI subsystem but the request did not get a response at all. To resolve this issue, try to restart the target machine and the system that runs the PRTG probe. For more information, see https://kb.paessler.com/en/topic/1093
PE056Multiple NetFlow sources.NetFlow sensors
PE057The NetFlow sensor has detected flows from multiple sources like IP addresses or observation domains. If you changed the configuration on the exporter device, you have to wait 10 minutes (NetFlow v5) to 30 minutes (NetFlow v9) until the new source is accepted.NetFlow sensors
PE058The interface you want to monitor is disconnected:SNMP Traffic sensor
PE059OK. The interface has been deactivated. %sAmazon CloudWatch sensor (deprecated)
PE060No monitoring statistics have been returned. To resolve this issue, make sure that the instance you want to monitor is running and that monitoring is enabled.Amazon CloudWatch sensors
PE061The host's system returned an invalid value for total memory: %s
To resolve this issue, enable an alternative query method in the WMI Alternative Query options of your sensor settings. For more information, see https://kb.paessler.com/en/topic/1093
WMI/SSH memory
PE062There has been a timeout because the sensor did not receive any data packets. To resolve this issue, try the QoS reflector script. For more information, see https://kb.paessler.com/en/topic/61176Quality of Service (QoS) sensors
PE063The sensor could not determine the state of the Hyper-V virtual machine. The reason might be that the virtual machine was renamed. In this case, you need to create a new Hyper-V sensor.
PE064The Hyper-V virtual machine is running.
PE065The Hyper-V virtual machine is turned off.
PE066The Hyper-V virtual machine is paused.
PE067The Hyper-V virtual machine is in a saved state.
PE068The sensor could not find the Hyper-V virtual machine. To resolve this issue, check if the virtual machine might be powered off. Also make sure that the virtual machine does not contain a slash or backslash in its name.
PE069 - PE074These error messages are deprecated.
PE075The .NET Framework is not installed on your probe system.
PE076The returned DNS record is not an 'A' record. To resolve this issue, leave the IP Address field empty.
PE077Getting metric statistics from 'monitoring.amazonaws.com' has timed out.
PE078The WMI query has returned more than one record. This indicates that the result was not properly restricted. For more information, see https://kb.paessler.com/en/topic/1093WMI/SQL query
PE079This error message is deprecated.
PE080The access has been denied. To resolve this issue, check your access keys in the Credentials for Amazon CloudWatch section of the device settings.Amazon CloudWatch sensors
PE081There were too many Syslog messages during the last scanning interval. Syslog messages have been dropped.Syslog Manager
PE082The sensor has dropped NetFlow data. To resolve this issue, make sure that you set an Active Flow Timeout in the sensor settings that is one minute greater than the flow timeout value that you set in the target device. For more information, see https://kb.paessler.com/en/topic/66485
PE083The NetFlow sensor has received and dropped flows with a time stamp older than the timespan defined by the active flow timeout. To resolve this issue, make sure that the sensor's Active Flow Timeout setting matches the flow timeout set in the flow exporter device. For more information, see https://kb.paessler.com/en/topic/66485
PE084This error message is deprecated.
PE085The target server did not return a valid time. To resolve this issue, use a packet analyzing tool and do a trace of the NTP packets to check if all fields are correctly populated.SNTP (Simple Network Time Protocol)
PE086The shared resource you want to monitor cannot be found.WMI Share sensor
PE087The external .exe file or script has not returned a response.EXE/Script sensor
PE088The query returned implausible data that cannot be processed. The reason might be that the WMI system does not send any capacity information. For troubleshooting solutions, see https://kb.paessler.com/en/topic/3713Volume sensors
PE089The port could not be opened for this sensor. To resolve this issue, check that you use different, unique ports for each QoS sensor so that packets can be correctly assigned. Also check that the port is opened in your firewall.QoS (Quality of Service) sensors
PE090The UDP port could not be opened. To resolve this issue, make sure that the port is not in use. Also make sure that the port is opened in your firewall or create respective NAT rules for this port.SNMP Trap Manager/Syslog Manager
PE091The UDP port %s could not be opened. To resolve this issue, make sure that the port is not in use. Also make sure that the port is opened in your firewall or create respective NAT rules for this port.SNMP Trap Manager/Syslog Manager
PE092The access has been denied. To resolve this issue, specify a username and password in the Credentials for Windows Systems section of the device settings.EXE/Script sensors
PE093Content changed: %s
PE094The device you want to monitor is not compatible. The sensor cannot parse the reply data.SSH
PE095The access has been denied. To resolve this issue, check your Credentials for Windows Systems in the device settings.EXE user
PE096The host's system is unable to process the command of PRTG: "%s"SSH
PE097There is an issue with port 22. SSH access via this port is not available.
PE098The host's WMI system returns invalid data: %s
To resolve this issue, use Paessler WMI Tester with the correct query from https://kb.paessler.com/en/topic/8783 to test the accessibility of your WMI counters.
PE099The Oracle SQL statement must not contain quotation marks.
PE100The file you want to monitor is too old.Folder sensor
PE101File too youngFolder sensor
PE102Multiple fields are invalid.WMI multi-query
PE103DHCP offer from %sDHCP sensor
PE104This sensor requires that the .NET Framework version %s is installed on the system that runs the PRTG probe. For more information, see https://kb.paessler.com/en/topic/60543
PE105No Response (%s). To resolve this issue, check that the HTTP request is not blocked by a firewall or by incorrect proxy settings. Also check if the monitored website uses SSL and may require a client certificate.
PE106Private key file not found.WMI File sensor
PE107Latest operation return code: TimeoutCisco IP SLA sensor
PE108Latest operation return code: No connectionCisco IP SLA sensor
PE109The IP SLA is not in service. The reason might be that it is stopped, pending, restarting, or otherwise inactive.Cisco IP SLA sensor
PE110The flow processor buffer is full. The reason might be that PRTG is not able to process the flows. To resolve this issue, consider using remote probes. Also reduce the filtering and toplist parameters. For more information on the total number of flows that PRTG can process, see https://kb.paessler.com/en/topic/20613Flow timeout
PE111The flow processor has dropped flows. The reason might be that PRTG is not able to process the incoming flows fast enough. To resolve this issue, consider using remote probes. Also try to optimize your include, exclude, and filter rules. For more information, see https://kb.paessler.com/en/topic/24973Flow timeout
PE112No DNS record could be found.
PE113This sensor does not support IPv6.
PE114This sensor does not support IPv4.
PE115The probe system does not support IPv6.
PE116The probe system does not support IPv4.
PE117This sensor type is not supported by probes that are running on Linux.
PE118 - PE119These error messages are deprecated.
PE120Filtering the received events for multipe event IDs is not supported for WMI Event Log sensors.WMI Event Log sensor
PE121The request has timed out because the sensor is waiting for mutex. To resolve this issue, change your vCenter settings to accept more connections at the same time. Also try to distribute your VMware sensors among several remote probes. For more information, see https://kb.paessler.com/en/topic/30643
PE122This sensor type is deprecated and will not work with the current version of PRTG. We recommend that you pause it to keep its historic data. To continue monitoring, add a Citrix XenServer Virtual Machine sensor.Xen sensor deprecated; Citrix XenServer Virtual Machine sensor
PE123There is no active connection for this remote IP address. The reason might be an issue with Cisco's SNMP component. The data that PRTG receives from the device is incorrect. To resolve this issue, see https://kb.paessler.com/en/topic/59643SNMP Cisco ASA VPN Traffic sensor
PE124The sensor could not access the mailbox you want to monitor. The reason might be a connection limit of the target mail server. To resolve this issue, check if you entered valid credentials in the sensor settings. Also run the email checks in smaller batches by creating schedules.IMAP sensor
PE125This sensor type is deprecated and will not work with the current version of PRTG. We recommend that you pause it to keep its historic data. To continue monitoring, add a VMware Virtual Machine (SOAP) sensor.VMware sensor deprecated; VMware Virtual Machine (SOAP) sensor
PE126This sensor type is deprecated and will not work with the current version of PRTG. We recommend that you pause it to keep its historic data. To continue monitoring, add a VMware Host Hardware (WBEM) sensor and a VMware Host Performance (SOAP) sensor, for example.VMware Health sensor deprecated; VMware Host Hardware (WBEM) sensor; VMware Host Performance (SOAP) sensor
PE127An unknown error occured. The sensor did not return an error message.
PE128This sensor requires that the Dell Modular Disk Storage Manager is installed on the system that runs the PRTG probe. You will find it on the resource CD for your device.DELL MDI sensors
PE129PRTG could not run the script or the output could not be parsed (%s).SSH Script sensor
PE130This 64-bit process uses more than 4 GB. The reason might be Windows limiting 64-bit counters to 32-bit values. For more information, see https://kb.paessler.com/en/topic/1073Windows Process sensor
PE131The WMI device is responding very slowly to WMI requests. To resolve this issue, restart the target computer. Also increase the scanning intervals of your WMI sensors and consider using remote probes for load balancing.WMI sensors
PE132Response not well-formed: "%s"EXE sensors
PE133PRTG could not find the file system (%s). The device does not provide any data for the specified index.SNMP NetApp Disk Free sensor
PE134 - PE138These error messages are deprecated.
PE139The storage of the device is almost full.SNMP NetApp Disk Free sensor
PE140PRTG could not find the connection. The device does not provide any data for the specified index.SNMP NetApp Disk Free sensor
PE141The network interface (%s) could not be found on the device.SNMP NetApp Network Interface sensor
PE142The service (%s) could not be found on the device.SNMP NetApp License sensor
PE143The license for service "%s" has expired.SNMP NetApp License sensor
PE144The license for service "%s" will expire soon.SNMP NetApp License sensor
PE145 - PE154These error messages are deprecated.
PE155The disk with the distinguished name "%s" could not be found.
PE156The disk with the serial number "%s" could not be found. The reason might be that the respective disk was replaced or that there was a server restart. To resolve this issue, remove the respective sensor and add it anew.SNMP HPE ProLiant Physical Disk sensor
PE157The network adapter with the MAC address "%s" could not be found.SNMP HPE ProLiant Network Interface sensor
PE158 - PE161These error messages are deprecated.
PE162The condition of one of the power supplies is "%s".SNMP HPE ProLiant System Health sensor
PE163The status of one of the power supplies is "%s".SNMP HPE ProLiant System Health sensor
PE164The number of open or closed ports has changed.Port sensor
PE165 - PE167These error messages are deprecated.
PE168The sensor could not parse the content of the returned value.HTTP Content sensor
PE169This error message is deprecated.
PE170At least one fan is not ok, but "%s".SNMP Cisco System Health sensor
PE171At least one power supply is not ok, but "%s".SNMP Cisco System Health sensor
PE172This error message is deprecated.
PE173{Empty String}WMI Custom String sensor
PE174The HTTP request did not return enough values (%s). The reason might be that there are more channels for monitoring than monitored values. When adding the sensor, the Number of Channels setting must match the number of returned values. For more information, see https://kb.paessler.com/en/topic/53193HTTP Content sensor
PE175The domain is available.File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows
PE176The domain is not available (%s).File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows
PE177The domain login is allowed.File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows
PE178The domain login is denied (%s). To resolve this issue, enter Credentials for Windows Systems with sufficient access rights in the device settings.File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows
PE179Impersonation was allowed.File sensor, Folder sensor, Event Log (Windows API) sensor
PE180Impersonation was denied. To resolve this issue, enter Credentials for Windows Systems with sufficient access rights in the device settings.File sensor, Folder sensor, Event Log (Windows API) sensor
PE181This sensor requires that PowerShell 2.0 or higher is installed on the probe system (%s).PowerShell sensors (not used anymore as of PRTG 18.1.37)
PE182The file exists.File sensor
PE183The sensor could not find any VPN connection that uses IPsec.SNMP Cisco ASA VPN sensors
PE184The sensor could not find any ADSL connection on the monitored device.SNMP Cisco ADSL sensor
PE185The sensor could not find any Cisco system health metrics on the monitored device. The reason might be that the device does not provide data for the OIDs that the sensor queries. To resolve this issue, check if Cisco has dedicated MIB files for the device you want to monitor.SNMP Cisco System Health sensor
PE186The sensor could not find any NetApp enclosure metrics on the monitored device.SNMP NetApp Enclosure sensor
PE187The sensor could not find any matching data on the monitored device. To resolve this issue, check if SNMP is enabled on the device. Also check if the Dell OpenManage Server Administrator is correctly installed on the target server. Or check if the needed OIDs can be reached. For more information, see https://kb.paessler.com/en/topic/68040Several SNMP hardware sensors
PE188The sensor could not find any disks on the monitored device. The reason might be a Windows security feature that prevents automatic integration of the Windows SNMP agent with the components from IBM. To resolve this issue, see https://kb.paessler.com/en/topic/73914SNMP physical disk sensors
PE189The sensor could not find any network adapters on the monitored device.Traffic sensors
PE190The sensor could not find any NetApp licensing information on the monitored device.SNMP NetApp License sensor
PE191No virtuozzo containers detected on this device.Virtuozzo sensor (deprecated)
PE192The sensor could not detect any IP SLAs on the monitored device. To resolve this issue, first enable SNMP and IP SLA on the Cisco device you want to monitor, then add the sensor anew. For more information, see https://kb.paessler.com/en/topic/45403Cisco IP SLA sensor
PE193For the HELO identifier, only ASCII characters (except CR and LF) are allowed. Make sure that you only use valid characters.SMTP sensor
PE194The sensor could not find any IBM system health metrics on the monitored device. The reason might be a Windows security feature that prevents automatic integration of the Windows SNMP agent with the components from IBM. To resolve this issue, see https://kb.paessler.com/en/topic/73914SNMP IBM System X System Health sensor
PE195The measuring point (%s) could not be found on the device
PE196PRTG could not find the sssu.exe file from the HPE P6000 Command View Software on the system that runs the PRTG probe. To resolve this issue, make sure that this program is installed on the system that runs the PRTG probe. If you do not want to install the whole Command View, see https://kb.paessler.com/en/topic/55983Enterprise Virtual Array sensor
PE197The sensor could not establish a connection. To resolve this issue, check if the VPN you want to monitor is connected. Also check if you correctly configured the Identification Method in the sensor settings.SNMP SonicWALL VPN Traffic sensor
PE198The sensor could not find any connections. Make sure that the VPN you want to monitor is up and running.SNMP SonicWALL VPN Traffic sensor
PE199The returned data is in the wrong format (%s).SNMP QNAP sensors
PE200The sensor could not find any volumes on the monitored device.Disk sensors
PE201The sensor could not find any logical units on the monitored device.SNMP NetApp Logical Unit sensor
PE202The sensor could not find the logical unit (%s) on the monitored device.SNMP NetApp Logical Unit sensor
PE203"%s" may fail soon
PE204The sensor could not find the chassis (%s).HP sensors
PE205The sensor could not retrieve any update data. To resolve this issue, make sure that your WSUS is correctly configured. Also try to restart the Windows Update service on the target system.Windows Updates Status (PowerShell) sensor
PE206PRTG could not start the HTTP push receiver. %sHTTP Push sensors
PE207This service is either not installed on the target system or it is stopped. To monitor a service and make sure that it is NOT running, see https://kb.paessler.com/en/topic/64529SNMP Windows Service sensor
PE208The regex did not match the string. To resolve this issue, check the correct definition of your regex with a test tool. Also make sure that the regex matches additional source code like HTML.Sensors using regular expressions
PE209The provided value is not a valid integer (%s).HTTP Push sensors
PE210No value was provided. %sHTTP Push sensors
PE211The provided value is not a valid float (%s).HTTP Push sensors
PE212The sensor could not find any %s on the SAN that you want to monitor. The reason might be that the SAN does not support a CLI over SSH.SSH SAN sensors
PE213The answer that the sensor received from the NetApp device contained invalid data.NetApp sensors
PE214The probe disk is full.Syslog Receiver sensor; SNMP Trap Receiver sensor
PE215PRTG has stopped Syslog monitoring and Trap monitoring.Syslog Receiver sensor; SNMP Trap Receiver sensor
PE216The returned data is in the wrong format.SSH SAN sensors
PE217The virtual machine with the GUID "%s" could not be found on the target system.SCVMM sensors (deprecated)
PE218The host with the GUID "%s"
could not be found on the target system.
SCVMM sensors (deprecated)
PE219The measurement for "%s" is not available. The reason might be a hardware issue.NetApp sensors
PE220The IPMI is not available.IPMI System Health sensor
PE221The login has failed. Make sure that you entered the correct username and password.IPMI System Health sensor
For troubleshooting, also see The IPMI System Health sensor cannot be added and shows the error code PE221. What can I do?
PE222The latest push message that the sensor received is older than the specified time threshold allows.HTTP Push sensors
PE223No metrics found.SNMP IBM System X System Health sensor
PE224The system you want to monitor does not provide any data for its CBQoS instances.SNMP Cisco CBQoS sensor
PE225The number of temperature sensors does not match the number of temperature measurements.
PE226The number of fans does not match the number of fan measurements.SNMP NetApp Enclosure sensor
PE227The number of voltage sensors does not match the number of voltage measurements.SNMP NetApp Enclosure sensor
PE228The number of current sensors does not match the number of current measurements.SNMP NetApp Enclosure sensor
PE229This sensor requires that the Dell Modular Disk Storage Manager is installed on the system that runs the PRTG probe. You will find it on the resource CD for your device. For more information, see https://kb.paessler.com/en/topic/38743Dell PowerVault MDi sensors
PE230Failed to execute the SMCli command.Dell PowerVault MDi sensors
PE231The returned JSON does not match the expected structure (%s).Custom script sensors
PE232There has been an error reading the response. The JSON is invalid.Custom script sensors
PE233The returned XML does not match the expected schema.Custom script sensors
PE234The interface is disconnected. %sSNMP Traffic sensor
PE235Classes not found: "%s"WMI sensors
PE236Instances not found: "%s"WMI sensors
PE237 - PE239These error messages are deprecated.
PE240There has been a timeout while reading file: %s. To resolve this issue, increase the sensor's scanning interval.File Content sensor
PE241There has been a timeout while waiting for the response of the SAN. To resolve this issue, restart the SSH controller.SSH SAN sensors
PE242XML: The channel name must not be empty.EXE/Script Advanced sensor
PE243You cannot use this sensor to monitor localhost (127.0.0.1).Cloud HTTP sensor; Cloud Ping sensor
PE244The sensor does not get a response from the device you want to monitor. The reason might be that the SNMP credentials are wrong or that the device does not support the required uptime OID (1.3.6.1.2.1.1.3.0) for traffic sensors. To resolve this issue, check the SNMP access rights of the device or contact the device vendor.SNMP (Traffic sensors)
PE245PRTG could not open port %s. The reason might be that another process is using the port on the machine that PRTG is running on. To resolve this issue, see https://kb.paessler.com/en/topic/71371Syslog Receiver sensor; SNMP Trap Receiver sensor
PE246The sensor exceeded the maximum number of 50 users. For more information, see https://kb.paessler.com/en/topic/64053SNMP Cisco ASA VPN sensor
PE247PRTG could not find a table row matching the index that you specified when adding the sensor (%s). The reason might be that the value of the column that you selected has changed.SNMP Custom Table sensor
PE248The OID that you entered does not point to an SNMP table. To resolve this issue, manually add the OID to an SNMP Custom sensor or enter an OID that points to an SNMP table.SNMP Custom Table sensor
PE249The system you want to monitor does not support the OID you entered or the table is empty. Make sure that the OID you enter is in the correct format without the preceding dot.SNMP Custom Table sensor
PE250Structural error: %sSensors using the OAuth authorization method
PE251All channel names must be distinct.All sensors having more than 1 channel
PE252The installer found a legacy version of PRTG that cannot be directly updated because the integrated database has to be converted first. To resolve this issue, see https://kb.paessler.com/en/topic/65764Updates from PRTG versions 7 and 8
PE253Unexpected cloud error.Sensors and services involving cloud processes
PE254The configuration for the sensor is invalid. Make sure that you configure at least one channel.Business Process sensor
PE255The sensor could not connect to the Remote Registry Windows service of the target system. To resolve this issue, make sure that the service is running. Also make sure that you entered correct Credentials for Windows Systems in the device settings. For more information, see https://kb.paessler.com/en/topic/67824
PE256The volume "%s" that you want to monitor could not be found.SNMP Dell EqualLogic Logical Disk
PE257This sensor requires SNMP v2c or later. If you use SNMP v3, check your Credentials for SNMP Devices in the device settings.SNMP Dell EqualLogic Member Health
PE258This sensor type was removed from PRTG. For more information, see https://kb.paessler.com/en/topic/68227
PE259PRTG does not support checking inodes for ESX(i) hosts.SSH INodes Free sensor
PE260The character "%s" is not allowed in file names.Script sensors
PE261You cannot use this sensor type on the hosted probe, the local probe of a PRTG hosted by Paessler instance. To resolve this issue, add the sensor to a remote probe.PRTG hosted by Paessler
PE262PRTG could not initiate an SFTP session.SFTP Secure File Transfer Protocol sensor
PE263The sensor was not able to establish a connection for more than three successive scanning intervals. The reason might be corrupt performance counters or a damaged WMI stack on the target Windows system. To resolve this issue, see https://kb.paessler.com/en/topic/72969WMI sensors
PE264The data that the target WMI system returns is invalid and cannot be properly processed. This is not a PRTG issue but an issue of the device you want to monitor. For more information, see https://kb.paessler.com/en/topic/72969WMI sensors
PE265The sensor scan has timed out while getting file information. To resolve this issue, increase the sensor's scanning interval.Folder sensor
PE266The script parameters contain invalid characters. Only alphanumeric characters and ._-=/ are allowed. All other characters have to be surrounded by single (') or double (") quotes.
PE267Data storage is less than %s. To resolve this issue, see https://kb.paessler.com/en/topic/64628Probe Health sensor
PE268The sensor query was not successful because the target device returned no data for at least one channel. The reason might be an invalid OID.SNMP Cisco System Health sensor
PE269The queries for the following channel IDs returned no data: %sSNMP Cisco System Health sensor
PE270An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings.

Further PE Error Codes - Generic Errors

PE CodeMessage
PE10005This sensor type (%0:s) has been discontinued
and does not work with the current version of PRTG.
We recommend that you pause it to keep its historic data.
To continue monitoring, add a new %1:s sensor.
PE10040The connection settings or credentials are incomplete.
PE10050Channels are not available for this object
PE10101Sensor: Device %s returns no data.
PE10102Sensor (%0:s): Device %1:s returns no data.
PE10203Sensor (%0:s): PRTG has detected a change in identifier %1:s
PE10204Sensor (%0:s): PRTG could not find identifier %1:s
PE10305Sensor (%0:s): Parameter is missing %1:s
PE10306Sensor (%0:s): Parameter "%1:s" invalid "%2:s"
PE11101Sensor (%0:s) Descriptor: File is missing %1:s
PE11102Sensor (%0:s) Descriptor: File is invalid %1:s
PE11103Sensor (%0:s) Descriptor: Entry not found %1:s
PE11204Sensor (%0:s) Translator: Translator is invalid %1:s
PE11205Sensor (%0:s) Translator: Parameter is missing %1:s
PE11206Sensor (%0:s) Translator : Syntax error %1:s

Further PE Error Codes - Aggregation Errors (Sensor Factory sensor)

PE CodeMessage
PE2001The operation is not supported:
PE2002) is expected.
PE2003A value is expected.
PE2004The symbol is unknown:
PE2005The arrays have a different length.
PE2006The channel contains mixed value types. Use only delta values or absolute values.
PE2007Multiplication or division of two delta channels.
PE2008Comparison with delta channel.
PE2009( is expected.
PE2010, is expected.
PE2011An unmatched ) has been found.

Created on Feb 28, 2012 3:18:41 PM by  Volker Uffelmann [Paessler Support]

Last change on Jul 22, 2020 11:47:53 AM by  Florian Weik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

But what do they actually mean? My DNS server is constantly getting code: PE002, but the server is up and it is serving DNS. But I am constantly getting this but the code has no references to what might be the cause, no suggestions or ideas on what to look for. At this point it is just a set of ASCII codes.

PRTG offers a lot of data, but not a lot in the way or what that data is for. I just posed another question about an SNMP error I got on a switch a=ort and all it is is literally ERROR. Nothing else. What good does that do me?

Created on Sep 17, 2015 2:58:51 PM by  Metuckness (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

PRTG Network is a monitoring solution. The Probe sends out requests and the results are saved for analysis and later review. If the Probe sends out requests and does not receive an answer, that's exactly what the Code PE002-No response says. This will alert the System Administrator that something is not correct, maybe something important which would not have been recognized without a 24x7 monitoring solution. This error can have so many causes that it is simply not possible to pinpoint the correct solution next to the error message.

And the target is not able to tell PRTG what's the fault, as it's not even responding. We already cover a lot of troubleshooting guides and suggestions in our manual and our knowledge base, but if the device is not responding, you will need to see if all requirements are fulfilled and if all settings of the sensor are correct.

The same counts for the interface error. Normally, there are different error codes attached to the error message like i.e. Error #223 or Error #2003 which are generic messages from the SNMP daemon. Typing these error code into the knowledge base search field, will result in very detailed trouble shooting guides and will tell you why PRTG, or any other Monitoring Tool was not able to poll the requested information. If the interface of the target device is broken, monitoring solutions are dependent on which information is provided by the device itself. If there is no such information available, it cannot be monitored.

Our Technical Support and the community will assist you to find a solution to successfully add the sensor to your monitoring. You can open new Posts in the knowledge base or contact us directly via [email protected] We already added a lot of configuration hints to the sensor creation screen and will continue to do so in the future, but I'm afraid that we cannot cover every possible configuration characteristic in each of our customer's networks.

Best regards, Felix

Created on Sep 18, 2015 3:31:51 PM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, do you have more informations for this errorcode?

Code: PE266 Script parameters contain invalid characters outside of quotes. Try putting your parameters inside single/double quotes. Only alphanumeric characters and ._-=/ are allowed.

Created on Jul 14, 2017 8:13:01 AM by  fdegen (0) 1

Last change on Jul 14, 2017 10:10:42 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello fdegen,

It would be best if you could provide screenshots of the sensor's "Settings" tab and let us know which PRTG version you have currently running. You can also write us an email to [email protected] if you prefer not to post screenshots here.

Kind regards,

Erhard

Created on Jul 14, 2017 10:41:06 AM by  Erhard Mikulik [Paessler Support]



Votes:

0

Your Vote:

Up

Down

After updating PRTG server to version 18.1.38.11934, I get a PE180 error on an existing (and functioning) folder-sensor. The full error:

"Impersonation was denied (code: PE180)

Fair enough that the error is descriptive, but that's no excuse for not describing it. I hate it when a error code is shown, but is not described.

Created on Mar 19, 2018 10:53:17 AM by  gjhiddink (0)

Last change on Mar 19, 2018 12:29:01 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello gjhiddink,
thank you for your reply.

It may take a couple of days after the actual software implementation for the codes to be added here, but they are added as soon as the documentation team gets to it. Please excuse the delay. They have been added now.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Mar 23, 2018 8:15:36 AM by  Luciano Lingnau [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.