Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

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

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

Updated: November 1, 2018

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 log:

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 see the following Total Memory value:

.1.3.6.1.2.1.25.2.2.0 = INTEGER: -1118446524

Resolution

There is no direct resolution, as the issue is caused by 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 and Linux Servers: Agent option.

 

Last modified

Tags

Classifications

Public