Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

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-ret on Aug 15, 2017

Views: 1,397 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

Tags

Classifications

Public