This article applies to PRTG Network Monitor 19 or later
Limit of 100 Parallel EXE Sensors Error
If you have received the following error in your probe log
|Limit of 100 parallel .exe – Sensors reached for x times. DROPPING SEVERAL REQUESTS for system stability|
although the CPU load has not reached a critical level, this is not an error caused by exhaustion of your hardware, but rather a preventive limit that has been set within PRTG itself to avoid an unexpected termination of processes.
PRTG has a limit of 100 concurrent parallel EXE sensor-based scans. This includes PowerShell, batch, and other script-based custom sensors.
Reason for the Limitation
Windows defines a limited user land memory space or desktop heap memory for each user, service, or process. This practically limits the number of parallel child processes that can be running at the same time, among other things.
The default values Windows defines for a process that is running as a local system causes the termination of random child processes when approximately 120 child processes are running. Depending on the task or function these killed processes were running at the termination time, the result could be fatal.
PRTG limits the maximum amount of concurrent parallel EXE-based scans to 100. This is because terminating processes, in particular with regards to the EXE-based sensors, can lead to corrupt systems because allocated semaphores or mutexes cannot be released, for example.
This limitation is designed to keep a smooth flow of the scans on the probe. Normally, this limitation only applies in exceptional cases, even when systems have a heavy load. This can be the case if, for example, the core probe is reconnected and as a result, an initial rescan is carried out in the course of the schedule sequence, or if a large number of target systems is restarted.
Move the EXE sensors to multiple remote probes
Moving these sensors to remote probes can relieve the core server. The core server then only has to make the calculations and preparations, and therefore does not have to actually execute the EXE sensors. For more information, see PRTG Manual: Remote Probes and Multiple Probes.
Increase the scanning interval
Increasing the scanning interval to 10 or 15 minutes, for example, can help distribute the sensors more efficiently. This is only useful when you have less than 1,000 EXE sensors deployed in your monitoring setup. For more information, see PRTG Manual: System Administration—Monitoring.
Note: These solutions are only a last resort if the other solutions could not solve the issue or are not applicable.
- To increase the limitation count in the probe in question, contact our support via the PRTG web interface under Setup | Contact Support.
- To increase the desktop heap size in Windows, you have to modify the heap allocation sizes accordingly.
Important: We do not recommend modifying the registry because incorrect modification can cause serious issues. Please ensure that you have backed up the registry before you continue. For more information, see How to back up and restore the registry in Windows.
- Open the registry editor.
- Navigate to the following registry subkey:
- Right-click the Windows entry and click Modify.
- In the Value Data section of the Edit String dialog box, locate the SharedSection entry. Increase the second value and the third value for this entry.
For more information, see the Microsoft article You may receive an "Out of Memory" error message because of the desktop heap limitation.
For more information on desktop heaps, see Desktop Heap Overview.