www.gsx.com | log in | register

Last update: . Author: Cyril LEROY .

Unexpected Error Occurs While Scanning SharePoint Servers

An unexpected error can occur when GSX Monitor attempts to collect SharePoint information via PowerShell sessions without enough memory allocated. A step may have been missed while configuring SharePoint prerequisites that would set a higher memory allocation limit for PowerShell sessions.

This article describes how to solve the error by modifying the appropriate PowerShell value at the SharePoint server level to increase the memory allocation limit.

GSX Monitor 10+ | SharePoint 2010 and 2013

Symptoms

  • Unexpected error has occurred, please contact support@gsx.com. 
  • SharePoint Test Connection results in Warning.  

How to Solve the Issue

The default PowerShell session memory limit is 512MB. The following procedure increases the maximum memory allocation for a PowerShell session to 1024MB as recommended in our prerequisites documentation.

  1. Logon to the SharePoint Server using an Administrator account.
  2. Open an elevated Windows PowerShell Prompt.
  3. To check the value for MaxMemoryPerShellMB, use the command:
    Get-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 
  4. If the value is not already 1024, enter the following command to change it:
    Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1024

The value has been modified and GSX Monitor can now scan this SharePoint server successfully.

Microsoft Related articles



Not finding what you are looking for?

Have more questions? Submit a request


Was this article helpful?

1 out of 1 found this helpful