I created a powershell script to run a time check of a Cisco device via plink.exe. This is a script was set up on another core and worked there, but can not get it to properly work on new PRTG core.

If I run from server directly in powershell everything works and device responds with proper results via the lookup file (xxx.ovl). When I look at the sensor on the PRTG console the channel does not show up and the sensor has a "No Channel" error.

Where axactly does the caneel info get loaded from? Is there a way to add a channel manually?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

Thank you for your message.

Regarding the issue with the custom sensor, I invite you to enable its debug logs by using the option Store result within its Settings tab. This way, at the next scanning interval the probe will automatically generate the log files under "<path>\Logs\sensors" (where <path> is displayed in PRTG Administration on the corresponding server) and we can see what your script returns to PRTG.

I also invite you to check the following:

  • On the probe server, the script is not blocked by Windows (Unblock checkbox missing in the Properties menu of the file)
  • The execution policy is the same as on the other PRTG server (for both 32 bit and 64 bit)

Regards.


May, 2022 - Permalink