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


PE233 and PE231 error after update to 18.2.39.1661

Votes:

0

Your Vote:

Up

Down

Hi,

after I updated our PRTG installation to version 18.2.39.1661 this morning, I got two custom EXE/XML Scripts that gives this error: XML: The returned XML does not match the expected schema. (code: PE233) -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)

Has someone any idea how to fix this?

custom-sensor exexml prtg

Created on Apr 19, 2018 9:11:49 AM by  DickVink (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello there,

We changed the behavior with command line parameters. Here is the corresponding section from the Release Notes:
We fixed a potential security issue with command line parameters for PowerShell scripts that affected EXE/Script sensors, EXE/Script Advanced sensors, as well as Execute Program notifications (CVE-2018-9276). We also fixed a potential security issue with sample custom notifications (CVE-2018-9278).

Note: The fix required changes to the handling of command line parameters. In certain cases, it will be necessary to adapt quoting with backticks (``) in the parameters field because PRTG will process quotes more accurately. Please use single or double quotes to escape special characters and whitespaces in the parameters fields.

Please let me know if there are more questions about this.


Kind regards,
Birk Guttmann, Tech Support Team

Created on Apr 19, 2018 2:42:49 PM by  Birk Guttmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

thanks for your response. The quotes in the parameters fixed the issue partially. I use a script to check licenses. In the parameters I then give an option -Portserver and after that a -Features option to give the differtent software to check the license for. The line looked like this: -PortServer [email protected] –Features A, B, C, D, etc.

I changed the line to -PortServer "[email protected]" -Features "A, B, C, D" but then it gives the whole name A, B, C, and gives the result for Feature A.

After that I changed to -Features "A", "B", "C" but then only Feature A was working. Does this mean that I have to put a sensor for each different Feature?

Kind regards,

Dick Vink

Created on Apr 23, 2018 10:57:32 AM by  DickVink (0) 1



Votes:

1

Your Vote:

Up

Down

Hi Dick,

For security reasons, arrays can no longer be transferred in this way. There are two possibilities:

1. Make a variable for each parameter. Please note, that you have to create those parameters in the powershell, too:
-FeatureA "A" -FeatureB "B" -FeatureC "C" -FeatureD "D"
2. Change the Powershell script to split the incoming string, with the separator ",": PRTG parameter: -Features "A,B,C,D" Powershell changes: [string]$featureIn $feature = $featureln.split("{,}")
Please let me know if one if the above fits your requirements.


Kind regards,
Birk Guttmann, Tech Support Team

Created on Apr 24, 2018 7:43:13 AM by  Birk Guttmann [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.