I have receiving this error on one of my exchange servers
I have changed the winrm settings on the exchange server , usign the method described in the solarwinds help article SolarWinds Knowledge Base :: WinRM/WinRS Connection Limitations
anyone know what I am missing?
utildayael in another thread was able to solve similar issues he was having by increasing the number of concurrent users, max shells per-user, and memory per-shell
utildayael wrote:So in short, adjust your WINRM settings to have 20 MaxConcurrentUsers, 20 MaxShellsPerUser, and 512MB for MaxMemoryPerShellMB.This completely solved the issue with shells never going away and running rampant!So... the link when you go to configure AppInsight that is on the same page as the auto-configure button goes to:http://www.solarwinds.com/documentation/en/flarehelp/sam/default.htmSpoiler. It's just the SAM admin guide. No mention of AppInsight for Exchange. I did some KB digging and found an article or two on it but I didn't seem to see anything specifically telling you to set the above settings to that so what development had me do... apparently isn't the "standard" install. I used the "configure server" button and it clearly did not set any of those items as they all had values vastly different.
utildayael wrote:
So in short, adjust your WINRM settings to have 20 MaxConcurrentUsers, 20 MaxShellsPerUser, and 512MB for MaxMemoryPerShellMB.
This completely solved the issue with shells never going away and running rampant!
So... the link when you go to configure AppInsight that is on the same page as the auto-configure button goes to:
http://www.solarwinds.com/documentation/en/flarehelp/sam/default.htm
Spoiler. It's just the SAM admin guide. No mention of AppInsight for Exchange. I did some KB digging and found an article or two on it but I didn't seem to see anything specifically telling you to set the above settings to that so what development had me do... apparently isn't the "standard" install. I used the "configure server" button and it clearly did not set any of those items as they all had values vastly different.
I ran in to the same issue and after several weeks of back and forth with support the final solution was to create a new Throttling Policy on the Exchange server and set the PowerShellMaxConcurrency value to 1000. I applied the newly created policy to the SAM poller user and viola, everything worked.
You can test your specific installation by checking your policies in the Exchange Shell: Get-ThrottlingPolicy | select identity,powershellmaxconcurrency
If your "default" policy is set to 10, change it to 15, wait 20 minutes for Exchange to update itself, re-poll. If the number on the error changes, then that's your problem. Reset back to "10" although 18 is the default, but there may be a reason you have this changed.
To create the new policy, just use the following (change as appropriate):
New-ThrottlingPolicy -Name "Orion AppInsight Polling" -PowerShellMaxConcurrency 1000
Set-ThrottlingPolicyAssociation -ThrottlingPolicy "Orion AppInsight Polling" -Identity orion_poller
Again, for me, this was the fix. WinRM settings were completely irrelevant and I set them back to their defaults after changing this with no issues.
Thanks
Looks like I can get the throttling policy but cant set or create new ones. Also aLTeReGo those settings did not work for me.
Looks like you have to have Organization Management permission in order create a new throttling policy (Client Access Permissions: Exchange 2010 Help). If you aren't the Exchange Admin, chances are you won't have that.
I do everything here, so I didn't even think about that part. Just ask your Exchange admin to make the changes. Assuming you have a "known" account that does the polling, they shouldn't have much of an issue with the idea of it getting more connections. I specifically created the throttling policy so that I didn't mess with the default and affect every user/application that accessed by Exchange environment.
ok so it was the maxshells causing the issue.
Even though the initial error said session limit 10 was reached, which none of my thresholds were set to 10....When I went in to configure application then clicked test it gave me the real number of shells it had open.
Hi - what do you type in as the -Identity for Set-ThrottlingPolicyAssociation command ?
Is it just the "short-hostname" of the Orion polling engine?
- Does it matter if polling engine is in another domain than exchange server that it is polling?
