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

Problems with Mutex



We use a Powershell-Script to determine some folder sizes on a machine because the builtin PRTG Sensor for folder size (using SMB) is too slow and can get the job done within the timeframe of 900s (maximum timeout). They are set at an intervall of 24 hours and are all using one Mutex so that they don't run simultaneously. Problem is that using Mutex the sensors are inexplicably trying to update the result during the night at about 03:40 and all sensors show the Mutex error (PE035) immediately after that. So not even one of the sensors produces a result. At least one of the sensors should produce a result, shouldn't it?

Can anyone help me please?

folder-sensor mutex-timeout powershell

Created on Nov 28, 2017 3:12:47 PM

1 Reply



I already replied to your actual support ticket :) The easiest way would be to use the HTTP Push Data (Advanced) Sensor and execute the script on the target host via a scheduled task. The output of the script needs to be slightly modified in order to push the data to PRTG instead of simply printing the channel outputs.

Kind regards,
Stephan Linke, Tech Support Team

Created on Nov 29, 2017 12:01:35 PM by  Stephan Linke [Paessler Support]

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.