A new Powershell sensor is being identified as invalid, but the shell output seems to be ok.

My custom Powershell sensor returns the following output when executed in the shell: PS D:\Programme\PRTG Network Monitor\Custom Sensors\EXE> .\Get-NSPSuccess.ps1 36:OK

The predefined PRTG custom sensor returns the following value when executed in the shell PS D:\Programme\PRTG Network Monitor\Custom Sensors\EXE> & '.\Demo Powershell Script - Returns a fixed integer value.ps1' 100:OK

The predefined is recognized correctly, but the first one isn't. I don't see, why the first integer is being identified as invalid.

Cheers, Thomas

I don't see the

Article Comments

Dear Thomas,

please try using the sensors option (in its 'Settings'-tab) to write the result on disk, as a "Sensor-Log". Hopefully this will help to troubleshoot the issue.

Best Regards.


Dec, 2010 - Permalink

I've upgraded to version 8. Version 8 provided more informations about the issue in the default view. The Powershell sensor script called a second Powershell script, which wasn't referenced using the full filepath. After changing the Powershell call to use a full filepath the sensor script works fine. Cheers.


Dec, 2010 - Permalink