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

VmwareSensor25 keeps crashing




We have 5 hardware sensors for Vmware - it's almost a 100% reproducible crash. When logged into the prtg server I refresh the sensor, watch vmwaresensor25.exe cycle to around 50-75 cpu usage - then werfault.exe takes over and reports on an error.

The following two events can be found in my event viewer every time this occurs.

Application: VMwareSensor25.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 724694AA (72420000) with exit code 80131506.

Faulting application name: VMwareSensor25.exe, version:, time stamp: 0x50be074a Faulting module name: clr.dll, version: 4.0.30319.296, time stamp: 0x50484aa9 Exception code: 0xc0000005 Fault offset: 0x000494aa Faulting process id: 0x1f78 Faulting application start time: 0x01ce83e6616c4b67 Faulting application path: C:\Program Files (x86)\PRTG Network Monitor\Sensor System\VMwareSensor25.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: 9fdc590e-efd9-11e2-b086-005056a30001

crash sensor vmware

Created on Jul 18, 2013 6:48:49 PM

3 Replies



In which interval are you scanning the vmware server? The new, ESX5.0 capable sensors scales with the number of cores and the performance of the core itself (see www.cpubenchmark.net to have a comparison) the probe has available. In our testlab we could monitor appr. 30 VMware Hosts/VMs and read the performance data and hardware status from 5 VMWare hosts in a 5 min scanning interval PER CPU CORE on the (remote) probe machine without any issues using a physical machine. Keep in mind that several things can have an impact to performance, especially in virtualized environments.

In this tests, we found that installing the optional .NET Framework Reliability Update (http://support.microsoft.com/kb/2600217) had an huge impact on performance and therefore we recommend installing this update on the PRTG Probe machines as well as on the core machine. Please check if this update is installed.

As the hardware-status sensor uses much more performance we recommend to set the scan-interval to 5 minutes for these for the number of sensors you are using. Depending on the total number of virtual machines the host-performance may have a scan-interval of 1 minute or 2 minutes.

Created on Jul 19, 2013 7:22:13 AM by  Aurelio Lombardi [Paessler Support]



We are on version 4.0 not 5.0 - Could this be the issue? And as you can see it's not a performance issue it's the actual sensor crashing, I placed the event viewer output as it is. We are only trying to use 4 sensors here for each Vmware Host in that specific cluster. Literally everytime we refresh the sensor no matter what interval we try it at it crashes on the spot - like clock work.

Created on Jul 19, 2013 11:12:04 AM




It should not matter on which ESX(i)-version your systems are running.

The Errorcode indicates that the problem is located within the .Net-Framework.
Please check if the system is up to date with the current patches.
Some people are reporting this error on low systemresources, too. It may happen if the .Net-Framework can't allocate memory (disk or RAM).
Are you running a Virus/Malware-Scanner on the machine? Please try to turn it off to try if the Problem still exists.

Kind Regards

Created on Jul 22, 2013 1:34:04 PM by  Dieter Loskarn [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.