Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > Server & Application Monitor (SAM) > Process Monitor - SNMP error: Value was either too large or too small for a UInt32

Process Monitor - SNMP error: Value was either too large or too small for a UInt32

Created by Chris Foley, last modified by MindTouch on Jun 23, 2016

Views: 29 Votes: 0 Revisions: 4

Overview

The following error appears when attempting to use the Process Monitor - SNMP monitor:

Value was either too large or too small for a UInt32.

Upon analysis of the application's debug file, we see the following:

DEBUG SolarWinds.APM.Probes.ProcessSNMPProbe - Received response for memory size - error code: 0
ERROR SolarWinds.APM.Probes.ProbeBase`1 - Unhandled exception.
System.OverflowException: Value was either too large or too small for a UInt32.

Environment

  • All SAM versions
  • All Windows versions

Cause 

The total memory on the system exceeds the allowable size of the SNMP value that reports memory size.

If you look at an SNMPWalk against the target,you will see the following Total Memory value:

.1.3.6.1.2.1.25.2.2.0 = INTEGER: -1118446524

Resolution

Unfortunately there is no resolution as it is a limitation in SNMP.  

Possible workarounds:

  • Use the Service Status - SNMP monitor, which does not monitor process memory usage and therefore does not collect total memory on the system.
  • Use a custom VB, Powershell or Perl script to gather the status of the process and then use a Script Monitor to run the said script.

 

Last modified
03:00, 23 Jun 2016

Tags

Classifications

Public