Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Powershell Monitors intermittently return Out Of Memory Exceptions

Powershell Monitors intermittently return Out Of Memory Exceptions

Created by Chris Foley, last modified by carolyn.mazenko on Oct 02, 2018

Views: 1,354 Votes: 0 Revisions: 6

Updated October 2, 2018


This article describes the issue when Windows PowerShell Monitors intermittently return Out of Memory exceptions.


  • SAM 6.2.x and later


Powershell runs out of memory for certain PowerShell scripts. The larger the script, the more CPU and memory resources are required to run it, which can exceed the abilities of the machine running the polling job.


Increase the amount of memory Powershell has by running the following command from a Powershell prompt:

set-item wsman:localhost\Shell\MaxMemoryPerShellMB {amount in MB}


To verify the current amount, run the following command:.

get-item wsman:localhost\Shell\MaxMemoryPerShellMB


Consider hosting the polling engine on a 64-bit system. 64-bit machines have better capabilities in terms of memory management so they can process larger files (for example, over 1 GB) than 32-bit machines. 



Last modified