Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

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,292 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