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


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

error-code pe prtg

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

Last change on May 14, 2019 7:21:28 AM by  Maike Behnsen [Paessler Support]



7 Replies

Accepted Answer

Votes:

2

Your Vote:

Up

Down

PE Error Codes - Overview

PE CodeMessageContext
PE001IP does not match (%0:s <> %1:s)DNS IPs do not match
PE002No responseDNS
PE003Not connectedRDP (Remote Desktop) sensor,
IMAP sensor
PE004No Remote Desktop running on this portRemote Desktop
PE005Not supportedIMAP sensor (can be used by others)
PE006Logon failure: unknown user name or bad passwordIMAP sensor
PE007Server does not support APOPPOP3 sensor
PE008File not foundWMI File sensor
PE009Process not foundWindows Process sensor;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE010Service not foundWMI Service sensor
PE011Service not running (%s)WMI Service sensor
PE012No DNS NameDNS
PE013Drive not foundWMI Free Disk Space (Multi Disk) sensor
PE014Request timed outTimeout waiting for WMI query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE015Connection could not be establishedWMI connection;
see My WMI sensors show errors with a PE code. What does that mean? and Why do I receive the sensor error message 'Connection could not be established (code: PE015)' for details
PE016No result setWMI query did not return any records;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE017Ambiguous result setWMI query returned too many records or too many fields (WMI Custom sensor);
see My WMI sensors show errors with a PE code. What does that mean? for details
PE018TimeoutEXE/Script sensor,
Windows Update Status (PowerShell) sensor,
IP on DNS Blacklist sensor
PE019Could not load DLL
PE020Content changed
PE021See history for details
PE022System Error %sEXE/Script sensors
PE023Protocol Error %sEXE/Script sensors
PE024Content Error %sEXE/Script sensors
PE025Invalid dataWMI query direct;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE026Invalid previous data samplesWMI query direct;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE027Record count does not match previous record countWMI query direct
PE028UNC Path not allowedWMI 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
PE034Simulated errorSimulate
PE035Timeout caused by wait for mutexMutex for EXE/Script sensors
PE036Could not create mutexMutex for EXE/Script sensors
PE037Query returned no recordsWMI/SQL query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE038Query returned more than one rowWMI/SQL query
PE039Unexpected connection dropConnection gracefully closed
PE040Device sends 64 bit counters as 32 bit values. Please switch to alternative query in WMI compatibility options.WMI processor;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE041Device sends inconsistent counter data. Please switch to alternative query in WMI compatibility options.WMI processor;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE042Too many 32bit overflows. Try a shorter scanning interval.WMI querydirect.process;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE043Network card not foundWMI network;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE044No field specified in WQLWMI/SQL query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE045Too many fields specified in WQLWMI/SQL query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE046Could not parse WQLWMI/SQL query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE047Could not open WQL file "%s"See My WMI sensors show errors with a PE code. What does that mean? for details
PE048Mail TimeoutRound trips
PE049No available interfaces on this deviceSNMP
PE050The number of interfaces found is too large. Please retry with a smaller OIDLIB.SNMP
PE051WMI request timed out unrecoverably. If the problem persists with this sensor consider pausing or deleting it.WMI;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE052Service restartedService
PE053Cannot activate server on the specified portSyslog/SNMP Trap
PE054WMI system overload. Please extend the scanning intervals of your WMI sensors and/or use remote probes for load balancing.WMI;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE055Sensor stopped due to WMI lockup. Can be restarted with pause and resumeWMI;
see My WMI sensors show errors with a PE code. What does that mean?
PE056Multiple Netflow SourceNetFlow
PE057The netflow sensor has detected flows from multiple sources (ip adresses and/or observation domains). In case of a configuration change at the exporter device you have to wait 10 min. (netflow 5) or 30 min. (netflow 9) until the new source is acceptedNetFlow
PE058The interface is disconnected:SNMP Traffic sensor
PE060No monitoring statistics returned. Make sure instance is running and monitoring is enabled.Amazon CloudWatch sensors
PE061The host's system returned an invalid value for Total Memory: %sWMI/SSH memory;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE062Timeout. No packets received.Quality of Service (QoS)
PE063The state of the VM could not be determined.Hyper-V Virtual Machine
PE064The VM is running.Hyper-V Virtual Machine
PE065The VM is turned off.Hyper-V Virtual Machine
PE066The VM is paused.Hyper-V Virtual Machine
PE067The VM is in a saved state.Hyper-V Virtual Machine
PE068The VM could not be found. Is it powered off?Hyper-V Virtual Machine
PE075.Net Framework not installed
PE076The returned DNS record is not an "A" record. To avoid this error message leave the "IP Address" field empty
PE077Timeout getting metric statistics from monitoring.amazonaws.com
PE078Query returned more than one recordWMI/SQL query;
see My WMI sensors show errors with a PE code. What does that mean? for details
PE080Access denied. Please check your access keys.Amazon CloudWatch sensors continued
PE081There have been too many Syslog messages during this interval. Messages have been dropped.Syslog Manager
PE082Netflow data droppedFlow timeout
PE083The NetFlow sensor has received and dropped flows with a timestamp older than the timespan defined by the active flow timeout. Ensure the active flow timeout from the sensor settings matches the flow timeout set in the flow exporter device.

For details, see What is the Active Flow Timeout in Flow sensors?
Flow timeout
PE085The server did not return a valid timeSNTP (Simple Network Time Protocol)
PE086Shared Resource not foundWMI Share sensor: Shared resource
PE087External EXE/Script did not return a responseEXE/Script sensor
PE088The query returned implausible data that cannot be processed.Volume sensors
PE089Port could not be opened for this sensor. Please note, that the port number must be unique for every QoS SensorQoS sensor
PE090UDP Port could not be opened.SNMP Trap Manager/Syslog Manager
PE091Could not open UDP Port %s. Please make sure this port is not in use.SNMP Trap Manager/Syslog Manager
PE092Please specify a username and password in the device settings (Credentials for Windows Systems)EXE/Script sensors
PE093Content changed: %sNew content changed message with placeholder
PE094Device is not compatible (cannot parse reply data).SSH
PE095Access denied. Please check your Windows credentials.EXE user
PE096The host's system is unable to process PRTG's command: "%s".'SSH wrong system
PE097Port 22 error. SSH not available.SSH port unavailable
PE098The host's WMI system is returning invalid data: %sWMI invalid data (with message)
PE099SQL Statement must not contain quotation marks.Oracle SQL statement
PE100File too oldFolder sensor file age check
PE101File too youngFolder sensor file age check
PE102Multiple fields invalid.WMI multi-query had no field results
PE103DHCP Offer from %sDHCP sensor
PE104This sensor requires the .NET Framework version %sEXE with dot.net
PE105No Response (%s)HTTP invalid response code
PE106Private Key file not foundWMI File sensor
PE107Latest operation return code: TimeoutIP SLA
PE108Latest operation return code: No connectionIP SLA
PE109IP SLA is not in service. (May be stopped, pending, restarting or otherwise inactive)IP SLA
PE110Flow processor buffer fullFlow timeout
PE111The flow processor has dropped flows. Try optimizing your include, exclude and filter rules (Most likely matches first, use brackets to structure the rule, use ip ranges and masks instead of seperate IPs)Flow timeout
PE112Record not foundDNS
PE113IPv6 not supported by this sensorIP version not supported
PE114IPv4 not supported by this sensorIP version not supported
PE115Probe system does not support IPv6IP version not supported
PE116Probe system does not support IPv4IP version not supported
PE117Sensor type not supported by probes running on LinuxIP version not supported
PE120Sorry, filtering for multiple Event IDs is not supported for WMI Eventlog Sensors.WMI Event Log sensor
PE121Timeout caused by wait for mutex. Consider distributing your VMware sensors across several probes! See https://kb.paessler.com/en/topic/30643 for more information.Mutex for ESX-EXE sensors
PE122Sorry, this sensor type is discontinued and will not work with the current version of PRTG. We recommend you pause it to keep its historic data. In order to continue monitoring, please add a new "Xen Virtual Machine" sensor.Xen sensor deprecated
PE123There is no active connection for this remote IP address.SNMP Cisco ASA VPN Traffic sensor;
see I get the error PE123 when using the Cisco ASA VPN Traffic sensor. What can I do?
PE124Could not access the mailboxIMAP content check
PE125Sorry, this sensor type has been discontinued and will not work with the current version of PRTG. We recommend you pause it to keep its historic data. In order to continue monitoring, please add a new "VMware Virtual Machine (SOAP)" sensor.VMware sensor (deprecated)
PE126Sorry, this sensor type has been discontinued and will not work with the current version of PRTG. We recommend you pause it to keep its historic data. In order to continue monitoring, please add a new "VMware Host Server Health (SOAP)" and a "VMware Host Server(SOAP)" sensor.VMware Health sensor (deprecated)
PE127An unknown error occured. The sensor did not return an error message.
PE128This sensor needs the Dell Modular Disk Storage Manager to be installed on the system the probe is running on. You will find it on the resource CD for your device.DELL MDI sensors
PE129Either the script was not runable, or the output could not be parsed (%s)SSH Script sensor
PE130This 64 bit process may use more than 4 GBWindows Process sensor
PE131Phlegmatic WMI device: This device seems to respond very slowly to WMI requests. Please restart the target computer and/or increase the scanning intervals of the WMI sensors. Monitoring this host via a Remote Probe might be another option.All WMI sensors
PE132Response not well-formed: "%s"EXE sensors
PE133A file system was found during sensor creation. The identifier of this filesystem was saved to identify it in a list of file systems. The device does not provide any data for the with the specified name.SNMP NetApp Disk Free sensor
PE139The storage of the device is almost full.SNMP NetApp Disk Free sensor
PE140Could not find the connection with the specified index.SNMP NetApp Disk Free sensor
PE141The network interface(%s) could not be found on the deviceSNMP NetApp Network Interface sensor
PE142The service(%s) could not be found on the deviceSNMP NetApp License sensor
PE143The license for service "%s" is expired.SNMP NetApp License sensor
PE144The license for service "%s" will expire soon.SNMP NetApp License sensor
PE156The disk with serial number "%s" could not be foundSNMP HP ProLiant Physical Disk sensor
PE157The network adapter with MAC address "%s" could not be foundSNMP HP ProLiant Network Interface sensor
PE162The condition of one of the power supplies is "%s"SNMP HP ProLiant System Health sensor
PE163The status of one of the power supplies is "%s"SNMP HP ProLiant System Health sensor
PE164Number of open/closed ports has changed.Port sensor
PE168Error parsing content.HTTP Content sensor
PE170At least one fan is not ok, but "%s"SNMP Cisco System Health sensor: bad fans
PE171At least one power supply is not ok, but "%s"SNMP Cisco System Health sensor: bad supply
PE173{Empty String}WMI Custom String sensor
PE174Request returned not enough values. (%s)HTTP Content sensor
PE175The domain is available.File, Folder, Event Log (Windows API) and other sensors on Windows
PE176The domain is not available (%s).File, Folder, Event Log (Windows API) sensors and other sensors on Windows
PE177The domain login is allowed.File, Folder, and Event Log (Windows API) sensors and other sensors on Windows
PE178The domain login is denied (%s).File, Folder, and Event Log (Windows API) sensors and other sensors on Windows
PE179Impersonation was allowed.File, Folder, and Event Log (Windows API) sensors: impersonation
PE180Impersonation was denied.File, Folder, and Event Log (Windows API) sensors: impersonation
PE181This sensor requires the PowerShell 2.0 (or higher) to be installed on the probe system. (%s)PowerShell sensors (not used anymore in PRTG 18.1.37 and later)
PE182The file exists!File sensor
PE183Could not find any VPN connection, that is using IPSec!SNMP Cisco ASA VPN sensor
PE184Could not find any ADSL connection on this device.SNMP Cisco ADSL sensor
PE185Could not find any Cisco System Health metrics on this device.SNMP Cisco System Health sensor
PE186Could not find any NetApp enclosure metrics on this device.SNMP NetApp Enclosure sensor
PE187Could not find any matching data on this device.Several SNMP hardware sensors;
see
Common Errors when Using Dell PowerEdge Sensors;

IBM System X sensors could not find any disk/data on this device (PE187/PE188/PE194)
PE188Could not find any disk on this device.SNMP physical disk sensors;
see
Common Errors when Using Dell PowerEdge Sensors;

IBM System X sensors could not find any disk/data on this device (PE187/PE188/PE194)
PE189Could not find any network adapter on this device.Traffic sensors
PE190Could not find any NetApp licensing information on this device.NetApp License sensor
PE191No virtuozzo containers detected on this device.Virtuozzo sensor
PE192No IP SLAs detected on this device.Cisco IP SLA sensor
PE193HELO Ident: Only ACII characters (except CR and LF) allowed.SMTP sensor
PE194Could not find any IBM System Health metrics on this device.IBM System Health sensor;
see IBM System X sensors could not find any disk/data on this device (PE187/PE188/PE194)
PE195The measuring point (%s) could not be found on the device.
PE196Could not find the sssu.exe on the probe system. Please make sure the Command View EVA is installed on the probe system. If you do not want to install the whole command view please follow the instruction from this knowledgebase article: https://kb.paessler.com/en/topic/55983Enterprise Virtual Array sensor
PE197Could not find the connection. Is the VPN connected? Is the identification method in the sensor settings configured correctly?SNMP SonicWALL VPN Traffic sensor
PE198Could not find any connection. Please make sure the VPN you want to monitor is up and running.SNMP SonicWALL VPN Traffic sensor
PE199The data returned is in the wrong format (%s).SNMP QNAP sensors
PE200Could not find any volume on this device.Disk sensors
PE201Could not find any logical unit on this device.SNMP NetApp Logical Unit sensor
PE202The logical unit (%s) could not be found on the deviceSNMP NetApp Logical Unit sensor
PE203"%s" may fail soonSeveral sensors
PE204The chassis (%s) could not be found.HP sensors
PE205Could not retrieve update data. Please make sure your WSUS is configured correctly.Windows Updates Status sensor
PE206Could not start http push receiver. %sHTTP Push sensors
PE207This service is either not installed on the target system or it is stoppedSNMP Windows Service sensor
PE208The Regex did not match the string.Sensors with regular expressions
PE209The value provided is not a valid integer (%s)HTTP Push sensors
PE210There was no value provided %sHTTP Push sensors
PE211The value provided is not a valid float (%s)HTTP Push sensors
PE212Could not find any %s on this system. The reason might be that it does not support CLI over SSH.SSH SAN sensors
PE213The answer received from the NetApp device contained invalid data.NetApp sensors
PE214Probe Disk FullSyslog and Trap Receiver sensors
PE215Syslog and Trap monitoring has been stopped.Syslog and Trap Receiver sensors
PE216Wrong Data FormatSSH SAN sensors
PE217The vm with the guid "%s" could not be found on the target system.SCVMM sensors
PE218The host with the guid "%s" could not be found on the target system.SCVMM sensors
PE219The measurement for "%s" is not available. This may indicate a hardware issue.NetApp sensors
PE220IPMI not available.IPMI sensor
PE221Logon failure: unknown user name or bad password.IPMI sensor
PE222The latest push message that has been received is older than the threshold allowsHTTP Push sensors
PE223No metrics found.SNMP IBM System X System Health sensor
PE224The system does not provide any data for its CBQoS instancesSNMP Cisco CBQoS sensor
PE225Number of temperature sensors does not match number of temperature measurements.SNMP NetApp Enclosure sensor
PE226Number of fans does not match number of fan measurements.SNMP NetApp Enclosure sensor
PE227Number of voltage sensors does not match number of voltage measurements.SNMP NetApp Enclosure sensor
PE228Number of current sensors does not match number of current measurements.SNMP NetApp Enclosure sensor
PE229This sensor needs the Dell Modular Disk Storage Manager to be installed on the system the probe is running on. You will find it on the resource CD for your device.Dell PowerVault MDi sensors
PE230Failed to execute SMCli command.Dell PowerVault MDi sensors
PE231The returned json does not match the expected structure (%s).Custom script sensors
PE232Error reading response: Invalid JSON.Custom script sensors
PE233The returned xml does not match the expected schema.Custom script sensors
PE234OK. The interface is disconnected. %sSNMP Traffic sensor
PE235Class(es) not found: "%s"WMI sensors
PE236Instance(s) not found: "%s"WMI sensors
PE240Timed out while reading file: %s. Please increase the sensor's scanning interval.File Content sensor
PE241Timed out while waiting for SANs response. It might help to 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 and Cloud Ping sensor
PE244Sensor does not get a response from the device. Either SNMPv3 credentials are wrong or the device does not support the required uptime OID (1.3.6.1.2.1.1.3.0) for traffic sensors. This OID is mandatory by the SNMP RFC. Check the SNMP access rights in the device or contact the device vendor.SNMP (traffic sensors)
PE245Could not open port %sSNMP Trap sensor / Syslog sensor
PE246The sensor exceeded the maximum number of 50 users. See https://kb.paessler.com/en/topic/64053 for more information.SNMP Cisco ASA VPN sensor
PE247Could not find a table row matching the index you specified when adding the sensor (%s). The value of the column you selected might have changed.SNMP Custom Table sensor
PE248The OID you entered does not point to an SNMP table.SNMP Custom Table sensor
PE249The OID you entered is not supported by this system or the table is empty.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 not directly updatable legacy version of PRTG. See https://kb.paessler.com/en/topic/65764 for further assistance or contact [email protected]Updates from PRTG versions 7 and 8
PE253Unexpected Cloud ErrorSensors and services involving cloud processes
PE254Invalid configuration. You need to configure at least one channel.Business Process sensor
PE255Could not connect to the remote registry service of the target system. Make sure the service is running and the Windows credentials are correct.System information
PE256The volume with name "%s" could not be foundSNMP Dell EqualLogic Logical Disk
PE257This sensors requires SNMP v2c or later. Please check your SNMP Credentials in the device settings.SNMP Dell EqualLogic Member Health
PE258This sensor type has been removed from PRTG.Deprecated sensor types have been removed from PRTG and stopped monitoring with PRTG version 16.2.25. For details, see The PRTG Sensor Cleanup.
PE259Checking inodes is not supported for ESX(i) hosts.SSH INodes Free sensor
PE260Illegal character "%s" in file nameScript sensors
PE261You cannot use this sensor type on the hosted probe, the local probe of a PRTG instance hosted by Paessler.PRTG hosted by Paessler;
Add the sensor to a remote probe
PE262Failed to init SFTP session.SFTP Secure File Transfer Protocol sensor
PE263Sensor could not establish a WMI connection for more than 3 successive intervals. See https://kb.paessler.com/en/topic/72969 for more information.WMI sensors;
see PRTG WMI error messages for details
PE264The host's WMI system is returning invalid data. Please activate "Write sensor result to disk" in this sensor''s settings to find out what is going on.WMI sensors
PE265Scan timed out while getting file information.Folder sensor timeout
PE266Script parameters contain invalid characters outside of quotes. Try putting your parameters inside single/double quotes. Only alphanumeric characters and ._-=/ are allowed.SSH Script sensors;
other characters have to be surrounded by single (') or double (") quotation marks.
PE267Data storage is less than %s.Probe Health sensor;
see this article for details.
PE268Sensor query not successful. No data returned for at least one channel.SNMP Cisco System Health sensor (no channels because of an invalid OID)
PE269Queries for the following channel IDs returned no data: %sSNMP Cisco System Health sensor (cannot query data for one or more channels)

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

Last change on Jul 29, 2019 8:54:15 AM by  Maike Behnsen [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.