Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for Exchange error: Excessive number of PowerShell sessions and incomplete or missing results for some AppInsight for Exchange database metrics

AppInsight for Exchange error: Excessive number of PowerShell sessions and incomplete or missing results for some AppInsight for Exchange database metrics

Overview

This article provides brief information and steps to resolve the following AppInsight for Exchange error: 

Excessive number of PowerShell sessions and incomplete or missing results for some AppInsight for Exchange database metrics

Environment

All SAM versions

Resolution

Adjust your WINRM settings to have 20 MaxConcurrentUsers, 20 MaxShellsPerUser, and 512MB for MaxMemoryPerShellMB by Running the following commands on the Exchange Server that is being monitored by AppInsight for Exchange:

Note: Both the MaxConcurrentUsers and MaxShellsPerUser settings should be increased by 20 over the current environment settings to help eliminate this error. It is highly recommended to increase the MaxMemoryPerShellMB setting to 512 if it is currently at the default 128MB setting or less. This will help prevent session errors due to running out of memory.

 

 

  1. Open either a command prompt or PowerShell session in the Administrator context.

 

To view the WinRS settings, enter:
In CLI: winrm get winrm/config/winrs
In PS: Get-Item WSMan:\localhost\Shell* | Select-Object Name,Value

To modify MaxConcurrentUsers, enter:
In CLI: winrm set winrm/config/winrs @{MaxConcurrentUsers = "20"}
In PS: Set-Item WSMan:\localhost\Shell\MaxConcurrentUsers 20

To modify MaxShellsPerUser, enter:
In CLI: winrm set winrm/config/winrs @{MaxShellsPerUser="20"}
In PS: Set-Item WSMan:\localhost\Shell\MaxShellsPerUser 20

To modify MaxMemoryPerShellMB, enter:
In CLI: winrm set winrm/config/winrs @{MaxMemoryPerShellMB="512"}
In PS: Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 512

 

In the event the aforementioned changes do not resolve the issue, create a PowerShell throttling group.


Note: You will need to have Organization Managementpermission to alter or create a new throttling policy. 

Test your installation by checking your policies in the Exchange Shell by running the following command: 
Get-ThrottlingPolicy | select identity,powershellmaxconcurrency

If your default policy is set to 10, change it to 15 then wait 20 minutes for Exchange to update itself and then re-poll. If the number on the error changes, then you can identify that that is your problem. Reset the policy back to 10.

 

 

To create a new policy, use the following (change as appropriate):

New-ThrottlingPolicy -Name "Orion AppInsight Polling" -PowerShellMaxConcurrency 1000
Set-ThrottlingPolicyAssociation -ThrottlingPolicy "Orion AppInsight Polling" -Identity orion_poller
 

 

Last modified

Tags

Classifications

Public