Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > 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,476 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