Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

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 Su-Lyn Rosenberry on Aug 15, 2017

Views: 88 Votes: 0 Revisions: 6

Updated: August 15, 2017

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.
  • Poll the node using the Windows & Linux Servers: Agent option.

 

Last modified
08:45, 15 Aug 2017

Tags

Classifications

Public