PE Code | Message | Context |
PE001 | The IPs do not match. (%0:s <> %1:s) | DNS IPs |
PE002 | The target host does not respond. | |
PE003 | No remote desktop service is connected. To resolve this issue, check if the RDP port is accessible. | RDP (Remote Desktop) sensor; IMAP sensor |
PE004 | No remote desktop service is running on this port. | |
PE005 | Not supported. | IMAP sensor (can be used by others) |
PE006 | The login has failed. Make sure that you entered the correct username and password. | IMAP sensor |
PE007 | Your POP3 server does not support APOP. To resolve this issue, select a different authentication type for your POP3 server. | POP3 sensor |
PE008 | The 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 |
PE009 | The 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 |
PE010 | The 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 |
PE011 | The Windows service you want to monitor is not running (%s). | WMI Service sensor |
PE012 | No DNS name | |
PE013 | The 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 |
PE014 | The 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 | |
PE015 | Connection could not be established | WMI connection |
PE016 | The 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 | |
PE017 | The 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/1093 | WMI Custom sensor |
PE018 | Your 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 |
PE019 | Could not load DLL. | |
PE020 | The content has changed. | |
PE021 | See the history for details | |
PE022 | System Error: %s | EXE/Script sensors |
PE023 | Protocol Error: %s | EXE/Script sensors |
PE024 | Content Error: %s | EXE/Script sensors |
PE025 | The 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 |
PE026 | The 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/1093 | WMI query direct |
PE027 | The record count from the WMI query does not match the previous record count. | WMI query direct |
PE028 | UNC 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 |
PE029 | Logon failure: %s | SMB/File/Folder |
PE030 | Cannot access network share: %s | SMB/File/Folder |
PE031 | Cannot access file: %s | SMB/File/Folder |
PE032 | Cannot access folder: %s | SMB/File/Folder |
PE033 | Mailbox not found: %s | |
PE034 | The 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. | |
PE035 | The request has timed out because the sensor is waiting for mutual exclusion (mutex). For more information, see https://kb.paessler.com/en/topic/57133 | EXE/Script sensors |
PE036 | The sensor could not create a mutual exclusion (mutex). | EXE/Script sensors |
PE037 | The WMI/SQL query returned no records. For more information, see https://kb.paessler.com/en/topic/1093 | |
PE038 | The 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 | |
PE039 | The connection has dropped. | |
PE040 | The 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/1093 | WMI processor |
PE041 | The 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/1093 | WMI processor |
PE042 | There 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/1093 | WMI querydirect.process |
PE043 | The 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 |
PE044 | No 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/1093 | WMI/SQL query |
PE045 | Too 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/1093 | WMI/SQL query |
PE046 | WQL 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 |
PE047 | The 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 |
PE048 | The maximum trip time for an arriving email has timed out. | SMTP&IMAP Round Trip sensor; SMTP&POP3 Round Trip sensor |
PE049 | No 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. | |
PE050 | The number of interfaces found on this device is too large. To resolve this issue, retry using a smaller .oidlib file. | |
PE051 | The 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 | |
PE052 | Service restarted. | |
PE053 | PRTG cannot activate the server on the specified port. | Syslog/SNMP Trap |
PE054 | There 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. | |
PE055 | The 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 | |
PE056 | Multiple NetFlow sources. | NetFlow sensors |
PE057 | The 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 |
PE058 | The interface you want to monitor is disconnected: | SNMP Traffic sensor |
PE059 | OK. The interface has been deactivated. %s | Amazon CloudWatch sensor (deprecated) |
PE060 | No 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 |
PE061 | The 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 |
PE062 | There 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/61176 | Quality of Service (QoS) sensors |
PE063 | The 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. | |
PE064 | The Hyper-V virtual machine is running. | |
PE065 | The Hyper-V virtual machine is turned off. | |
PE066 | The Hyper-V virtual machine is paused. | |
PE067 | The Hyper-V virtual machine is in a saved state. | |
PE068 | The 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 - PE074 | These error messages are deprecated. | |
PE075 | The .NET Framework is not installed on your probe system. | |
PE076 | The returned DNS record is not an 'A' record. To resolve this issue, leave the IP Address field empty. | |
PE077 | Getting metric statistics from 'monitoring.amazonaws.com' has timed out. | |
PE078 | The 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/1093 | WMI/SQL query |
PE079 | This error message is deprecated. | |
PE080 | The 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 |
PE081 | There were too many Syslog messages during the last scanning interval. Syslog messages have been dropped. | Syslog Manager |
PE082 | The 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 | |
PE083 | The 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 | |
PE084 | This error message is deprecated. | |
PE085 | The 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) |
PE086 | The shared resource you want to monitor cannot be found. | WMI Share sensor |
PE087 | The external .exe file or script has not returned a response. | EXE/Script sensor |
PE088 | The 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/3713 | Volume sensors |
PE089 | The 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 |
PE090 | The 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 |
PE091 | The 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 |
PE092 | The 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 |
PE093 | Content changed: %s | |
PE094 | The device you want to monitor is not compatible. The sensor cannot parse the reply data. | SSH |
PE095 | The access has been denied. To resolve this issue, check your Credentials for Windows Systems in the device settings. | EXE user |
PE096 | The host's system is unable to process the command of PRTG: "%s" | SSH |
PE097 | There is an issue with port 22. SSH access via this port is not available. | |
PE098 | The 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. | |
PE099 | The Oracle SQL statement must not contain quotation marks. | |
PE100 | The file you want to monitor is too old. | Folder sensor |
PE101 | File too young | Folder sensor |
PE102 | Multiple fields are invalid. | WMI multi-query |
PE103 | DHCP offer from %s | DHCP sensor |
PE104 | This 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 | |
PE105 | No 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. | |
PE106 | Private key file not found. | WMI File sensor |
PE107 | Latest operation return code: Timeout | Cisco IP SLA sensor |
PE108 | Latest operation return code: No connection | Cisco IP SLA sensor |
PE109 | The IP SLA is not in service. The reason might be that it is stopped, pending, restarting, or otherwise inactive. | Cisco IP SLA sensor |
PE110 | The 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/20613 | Flow timeout |
PE111 | The 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/24973 | Flow timeout |
PE112 | No DNS record could be found. | |
PE113 | This sensor does not support IPv6. | |
PE114 | This sensor does not support IPv4. | |
PE115 | The probe system does not support IPv6. | |
PE116 | The probe system does not support IPv4. | |
PE117 | This sensor type is not supported by probes that are running on Linux. | |
PE118 - PE119 | These error messages are deprecated. | |
PE120 | Filtering the received events for multipe event IDs is not supported for WMI Event Log sensors. | WMI Event Log sensor |
PE121 | The 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 | |
PE122 | This 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 |
PE123 | There 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/59643 | SNMP Cisco ASA VPN Traffic sensor |
PE124 | The 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 |
PE125 | This 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 |
PE126 | This 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 |
PE127 | An unknown error occured. The sensor did not return an error message. | |
PE128 | This 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 |
PE129 | PRTG could not run the script or the output could not be parsed (%s). | SSH Script sensor |
PE130 | This 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/1073 | Windows Process sensor |
PE131 | The 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 |
PE132 | Response not well-formed: "%s" | EXE sensors |
PE133 | PRTG could not find the file system (%s). The device does not provide any data for the specified index. | SNMP NetApp Disk Free sensor |
PE134 - PE138 | These error messages are deprecated. | |
PE139 | The storage of the device is almost full. | SNMP NetApp Disk Free sensor |
PE140 | PRTG could not find the connection. The device does not provide any data for the specified index. | SNMP NetApp Disk Free sensor |
PE141 | The network interface (%s) could not be found on the device. | SNMP NetApp Network Interface sensor |
PE142 | The service (%s) could not be found on the device. | SNMP NetApp License sensor |
PE143 | The license for service "%s" has expired. | SNMP NetApp License sensor |
PE144 | The license for service "%s" will expire soon. | SNMP NetApp License sensor |
PE145 - PE154 | These error messages are deprecated. | |
PE155 | The disk with the distinguished name "%s" could not be found. | |
PE156 | The 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 |
PE157 | The network adapter with the MAC address "%s" could not be found. | SNMP HPE ProLiant Network Interface sensor |
PE158 - PE161 | These error messages are deprecated. | |
PE162 | The condition of one of the power supplies is "%s". | SNMP HPE ProLiant System Health sensor |
PE163 | The status of one of the power supplies is "%s". | SNMP HPE ProLiant System Health sensor |
PE164 | The number of open or closed ports has changed. | Port sensor |
PE165 - PE167 | These error messages are deprecated. | |
PE168 | The sensor could not parse the content of the returned value. | HTTP Content sensor |
PE169 | This error message is deprecated. | |
PE170 | At least one fan is not ok, but "%s". | SNMP Cisco System Health sensor |
PE171 | At least one power supply is not ok, but "%s". | SNMP Cisco System Health sensor |
PE172 | This error message is deprecated. | |
PE173 | {Empty String} | WMI Custom String sensor |
PE174 | The 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/53193 | HTTP Content sensor |
PE175 | The domain is available. | File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows |
PE176 | The domain is not available (%s). | File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows |
PE177 | The domain login is allowed. | File sensor, Folder sensor, Event Log (Windows API) sensor, and other sensors on Windows |
PE178 | The 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 |
PE179 | Impersonation was allowed. | File sensor, Folder sensor, Event Log (Windows API) sensor |
PE180 | Impersonation 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 |
PE181 | This 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) |
PE182 | The file exists. | File sensor |
PE183 | The sensor could not find any VPN connection that uses IPsec. | SNMP Cisco ASA VPN sensors |
PE184 | The sensor could not find any ADSL connection on the monitored device. | SNMP Cisco ADSL sensor |
PE185 | The 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 |
PE186 | The sensor could not find any NetApp enclosure metrics on the monitored device. | SNMP NetApp Enclosure sensor |
PE187 | The sensor could not find any matching data on the target device. To resolve this issue, check if the target device meets the requirements and if the required OIDs are reachable. | Several SNMP hardware sensors |
PE188 | The 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/73914 | SNMP physical disk sensors |
PE189 | The sensor could not find any network adapters on the monitored device. | Traffic sensors |
PE190 | The sensor could not find any NetApp licensing information on the monitored device. | SNMP NetApp License sensor |
PE191 | No virtuozzo containers detected on this device. | Virtuozzo sensor (deprecated) |
PE192 | The 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/45403 | Cisco IP SLA sensor |
PE193 | For the HELO identifier, only ASCII characters (except CR and LF) are allowed. Make sure that you only use valid characters. | SMTP sensor |
PE194 | The 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/73914 | SNMP IBM System X System Health sensor |
PE195 | The measuring point (%s) could not be found on the device | |
PE196 | PRTG 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/55983 | Enterprise Virtual Array sensor |
PE197 | The 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 |
PE198 | The sensor could not find any connections. Make sure that the VPN you want to monitor is up and running. | SNMP SonicWALL VPN Traffic sensor |
PE199 | The returned data is in the wrong format (%s). | SNMP QNAP sensors |
PE200 | The sensor could not find any volumes on the monitored device. | Disk sensors |
PE201 | The sensor could not find any logical units on the monitored device. | SNMP NetApp Logical Unit sensor |
PE202 | The sensor could not find the logical unit (%s) on the monitored device. | SNMP NetApp Logical Unit sensor |
PE203 | "%s" may fail soon | |
PE204 | The sensor could not find the chassis (%s). | HP sensors |
PE205 | The 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 |
PE206 | PRTG could not start the HTTP push receiver. %s | HTTP Push sensors |
PE207 | This 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/64529 | SNMP Windows Service sensor |
PE208 | The 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 |
PE209 | The provided value is not a valid integer (%s). | HTTP Push sensors |
PE210 | No value was provided. %s | HTTP Push sensors |
PE211 | The provided value is not a valid float (%s). | HTTP Push sensors |
PE212 | The 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 |
PE213 | The answer that the sensor received from the NetApp device contained invalid data. | NetApp sensors |
PE214 | The probe disk is full. | Syslog Receiver sensor; SNMP Trap Receiver sensor |
PE215 | PRTG has stopped Syslog monitoring and Trap monitoring. | Syslog Receiver sensor; SNMP Trap Receiver sensor |
PE216 | The returned data is in the wrong format. | SSH SAN sensors |
PE217 | The virtual machine with the GUID "%s" could not be found on the target system. | SCVMM sensors (deprecated) |
PE218 | The host with the GUID "%s" could not be found on the target system. | SCVMM sensors (deprecated) |
PE219 | The measurement for "%s" is not available. The reason might be a hardware issue. | NetApp sensors |
PE220 | The IPMI is not available. | IPMI System Health sensor |
PE221 | The 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? |
PE222 | The latest push message that the sensor received is older than the specified time threshold allows. | HTTP Push sensors |
PE223 | No metrics found. | SNMP IBM System X System Health sensor |
PE224 | The system you want to monitor does not provide any data for its CBQoS instances. | SNMP Cisco CBQoS sensor |
PE225 | The number of temperature sensors does not match the number of temperature measurements. | |
PE226 | The number of fans does not match the number of fan measurements. | SNMP NetApp Enclosure sensor |
PE227 | The number of voltage sensors does not match the number of voltage measurements. | SNMP NetApp Enclosure sensor |
PE228 | The number of current sensors does not match the number of current measurements. | SNMP NetApp Enclosure sensor |
PE229 | This 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/38743 | Dell PowerVault MDi sensors |
PE230 | Failed to execute the SMCli command. | Dell PowerVault MDi sensors |
PE231 | The returned JSON does not match the expected structure (%s). | Custom script sensors |
PE232 | There has been an error reading the response. The JSON is invalid. | Custom script sensors |
PE233 | The returned XML does not match the expected schema. | Custom script sensors |
PE234 | The interface is disconnected. %s | SNMP Traffic sensor |
PE235 | Classes not found: "%s" | WMI sensors |
PE236 | Instances not found: "%s" | WMI sensors |
PE237 - PE239 | These error messages are deprecated. | |
PE240 | There has been a timeout while reading file: %s. To resolve this issue, increase the sensor's scanning interval. | File Content sensor |
PE241 | There has been a timeout while waiting for the response of the SAN. To resolve this issue, restart the SSH controller. | SSH SAN sensors |
PE242 | XML: The channel name must not be empty. | EXE/Script Advanced sensor |
PE243 | You cannot use this sensor to monitor localhost (127.0.0.1). | Cloud HTTP sensor; Cloud Ping sensor |
PE244 | The 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) |
PE245 | PRTG 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/71371 | Syslog Receiver sensor; SNMP Trap Receiver sensor |
PE246 | The sensor exceeded the maximum number of 50 users. For more information, see https://kb.paessler.com/en/topic/64053 | SNMP Cisco ASA VPN sensor |
PE247 | PRTG 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 |
PE248 | The 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 |
PE249 | The 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 |
PE250 | Structural error: %s | Sensors using the OAuth authorization method |
PE251 | All channel names must be distinct. | All sensors having more than 1 channel |
PE252 | The 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/65764 | Updates from PRTG versions 7 and 8 |
PE253 | Unexpected cloud error. | Sensors and services involving cloud processes |
PE254 | The configuration for the sensor is invalid. Make sure that you configure at least one channel. | Business Process sensor |
PE255 | The 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 | |
PE256 | The volume "%s" that you want to monitor could not be found. | SNMP Dell EqualLogic Logical Disk |
PE257 | This 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 |
PE258 | This sensor type was removed from PRTG. For more information, see https://kb.paessler.com/en/topic/68227 |
PE259 | PRTG does not support checking inodes for ESX(i) hosts. | SSH INodes Free sensor |
PE260 | The character "%s" is not allowed in file names. | Script sensors |
PE261 | You cannot use this sensor type on the hosted probe of a PRTG Hosted Monitor instance. To resolve this issue, add the sensor to a remote probe. | PRTG Hosted Monitor |
PE262 | PRTG could not initiate an SFTP session. | SFTP Secure File Transfer Protocol sensor |
PE263 | The 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/72969 | WMI sensors |
PE264 | The 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/72969 | WMI sensors |
PE265 | The sensor scan has timed out while getting file information. To resolve this issue, increase the sensor's scanning interval. | Folder sensor |
PE266 | The script parameters contain invalid characters. Only alphanumeric characters and ".", "_", "-", "=", and"/" are allowed. All other characters have to be surrounded by single (') or double (") quotation marks. | |
PE267 | Data storage is less than %s. To resolve this issue, see https://kb.paessler.com/en/topic/64628 | Probe Health sensor |
PE268 | The 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 |
PE269 | The queries for the following channel IDs returned no data: %s | SNMP Cisco System Health sensor |
PE270 | An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. | |
PE271 | Component serial number has changed. Add the sensor anew to continue monitoring. | SNMP Rittal CMC III Hardware Status sensor |
PE272 | At least one channel uses a lookup that is not available or could not be loaded. | |
Add comment