What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags

View all Tags

PE233 & PE233 error



Hello everyone, recieving the following error for our Veeam Sensor Skript:

"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)"

After some researches i replaced the (" ") parameters with (``).
Set the Execution Policy.
Run the skript and it works.

What can be the problem?

Thank you in advance

exe-script-sensor json veeam-prtg-sensor-reloaded

Created on Jun 12, 2018 8:54:07 AM

Last change on Jun 12, 2018 10:22:14 AM by  Luciano Lingnau [Paessler]

6 Replies



Hello there,

Recently some changes were introduced regarding execution of Powershell scripts due to security reasons which has an impact on how parameters are processed.

Kind regards,


Created on Jun 13, 2018 11:36:16 AM by  Erhard Mikulik [Paessler Support]



Hello, thank you for your reply. We are already on verson, so this won't be the problem.

Created on Jun 13, 2018 11:44:35 AM



Yes, it is, because " " won't work anymore as fas as I have seen.

Created on Jun 13, 2018 11:52:00 AM by  Erhard Mikulik [Paessler Support]



Yes, thats why i already replaced them with ``.

Created on Jun 13, 2018 11:54:28 AM



You could set it back to the non-working variant and then enable "Write result to disk" in the sensor's "Settings" tab. With the next scan it will write one or several result-files into "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)" of your PRTG server (or on the Remote Probe if applicable). All files have the sensor's numeric ID in their filenames. The sensor ID can be found on the sensor's "Overview" tab. One of those files will show the the response of the script execution and possibly more details of what went wrong Note: In case you've configured a different data-path in PRTG Administration Tool, you need to look there for subfolder "Logs (Sensors)"

Created on Jun 13, 2018 12:31:54 PM by  Erhard Mikulik [Paessler Support]



For future people coming to this page, you need to enable PowerShell to allow remote scripts. On the remote PC, launch the Group Policy Editor and navigate to: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell

Enable "Turn on Script Execution" and set to "Allow local scripts and remote signed scripts".

Created on Dec 8, 2019 9:09:04 AM

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.