since the first of April, on one of our servers with PRTG, all TRACEROUTE probes started giving us the error PE087, in none of the other servers with PRTG has the same behavior, we tested manually running the traceroute program from the path c: \ Program Files (x86) \ PRTG Network Monitor \ Sensor System and it works perfect, but when checking the probe it throws us the indicated error, we already checked that the server had framework 3.5 and 4.5, what could be happening?

Article Comments

Hi there,

Did anything change on the PRTG host on April 1st? Does the custom sensor work if you deploy it anew?

You can also try to change the logon account of the "PRTG Probe Service" on the system to the user account which you use to manually execute the sensor via CMD.

Does it work then?

Best regards, Felix


Apr, 2018 - Permalink

Felix, first thank you for your prompt response. We did not make any changes on April 1st, we also tried to create a new sensor and it gave us the same result. We also tried to change the user that runs "PRTG Probe Service", and we obtained the same result. When I manually run the probe, it works for what we can see in CMD. The strangest behavior is because the sensor sometimes works and sometimes not, without us making any change in the configuration. This also happens with the httpfullsensor probes, the rest of the probes work without problems.


Apr, 2018 - Permalink

Hi there,

To get a better overview of your system, could you please forward so called Probe Status Files, this is described here.

You can send these files to support@paessler.com by referring to this Knowledge Base article.

Best regards, Felix


Apr, 2018 - Permalink