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

Scheduled Task Sensor - Ignoring exit code signalling task still running



I have a number of scheduled tasks I wish to monitor.

I have configured the Upper & Lower Error Limits to trigger on <> 0, because any condition other than 0x0 is a failure as far as these tasks are concerned. However, if the sensor interrogates the tasks while they are currently running, the ExitCode 0×41301 (267,009 in decimal) is returned and this is raising an Error.


Is there are a way to ignore this faux exit code?

exitcode prtg scheduled-task

Created on Jan 17, 2012 11:49:20 PM

1 Reply

Accepted Answer



There is a possibility, to get this bahavior. It is a little tricky, though. Please set up your Scheduled Task sensor, as you are used do not use channel limits.

Now add a Sensor Factory sensor with the following settings:

Channel Definition: #1:state channel(<sensorid>,3)

Error Handling: Use custom formula

Status Definition: (channel(<sensorid>,3)<>0)AND(channel(<sensorid>,3)<>267009)

You need to replace <sensorid> with your sensorid. It can be found in the overview tab of your sensor in the line below the channel name. You can also replace "state" by any channelname, you want to use.

Now, you can use a State Trigger on your Sensor Factory sensor for your notifications.

Please keep in mind, that "Scan now" will not have any effect on the Sensor Factory. It will take some seconds, until the new channel value is correctly shown in the factory.

We're aware, that it will be some work, to add a factory for every task, you want to monitor, but we can't think of any way how to change the sensor without negativly affecting other customers, that rely on the sensor behavior as it is right now.

Created on Nov 8, 2012 9:58:09 AM by  Johannes Herrmann [Paessler Support] (1,360) 2 2

Last change on Nov 8, 2012 10:01:52 AM by  Johannes Herrmann [Paessler Support] (1,360) 2 2

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.