Click on the Category button to get more articles regarding that product.
Error:
1000 requests per 2 seconds in Exchange GUI or if you open Powershell worst case
-
You open Exchange Powershell and the Shell “Jumps” to another Server (Like a CAS or other Mailbox Server) > Not the Local one
-
You open the Exchange GUI and you can’t connect / Expand the on Premise Server
|
Error: MTA reports error “system load quota of 1000 requests per 2 seconds has been exceeded” |
|
Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the system quota. The next request from this user will not be approved for at least 1812767488 mi lliseconds. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption + FullyQualifiedErrorId : PSSessionOpenFailed |
|
Event ID: 32784 |
|
Source: Microsoft-Windows-PowerShell Computer: exch-cas121-switzerland-admin WSMan reported an error with error code: -2144108120. Error message: Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the system quota. The next request from this user will not be approved for at least 1795919616 milliseconds. For more information, see the about_Remote_Troubleshooting |
Quick Solution:
Try another Exchange Server (CAS, Mailbox or maybe a IT management Server with Exchange Tool installed).
Solution quick:
Open IIS Konsole
Go to “Application Pools”
Select
MSExchangePowershellAppPool
On right side “Select” Recycle
Please check and re-open the Exchange GUI.
If this does not solve it please open an elevated cmd.exe shell and run:
Iisreset /noforce
Please check and re-open the Exchange GUI.
If this does not help run:
Iisreset
If this does not help restart the server that has the Error in Event.
Reason:
Could be a third party tool like an E-Mail Archive (Symantec EV [Enterprise Vault]?) or external Blackberry Server (Just something that PULLS E-Mails from the Exchange) and modifies the Throttling Policy. We however compared running customer to non-running and did not see any difference in the values if you run.
Get-ThrottlingPolicy
Or
Get-ThrottlingPolicy | fl powershellmaxconcurrency
One value would be “powershellmaxconcurrency”. We see a value of 18 in Exchange 2010 SP3 some describe values of 5 (Maybe earlier Exchange 2010 or RTM, Dell KB does so). This value is described in different KB articles BUT we can’t confirm that this value is the source. Because all our larger customers have a Value of 18 there. Only the Backup Exec Throttling Policy has a value of $null and thus unlimited numbers of Shells.
|
DefaultThrottlingPolicy Throttling Policy |
|
AnonymousMaxConcurrency : 1 AnonymousPercentTimeInAD : AnonymousPercentTimeInCAS : AnonymousPercentTimeInMailboxRPC : IMAPMaxConcurrency : IMAPPercentTimeInAD : IMAPPercentTimeInCAS : IMAPPercentTimeInMailboxRPC : OWAMaxConcurrency : 5 OWAPercentTimeInAD : 30 OWAPercentTimeInCAS : 150 OWAPercentTimeInMailboxRPC : 150 PowerShellMaxConcurrency : 18 PowerShellMaxTenantConcurrency : PowerShellMaxCmdlets : PowerShellMaxCmdletsTimePeriod : ExchangeMaxCmdlets : PowerShellMaxCmdletQueueDepth : PowerShellMaxDestructiveCmdlets : PowerShellMaxDestructiveCmdletsTimePeriod : RCAMaxConcurrency : 20 RCAPercentTimeInAD : 5 RCAPercentTimeInCAS : 205 RCAPercentTimeInMailboxRPC : 200 CPAMaxConcurrency : 20 CPAPercentTimeInCAS : 205 CPAPercentTimeInMailboxRPC : 200 MessageRateLimit : RecipientRateLimit : ForwardeeLimit : CPUStartPercent : 75 AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) |
|
EnterpriseVault Throttling Policy |
|
AnonymousMaxConcurrency : 1 AnonymousPercentTimeInAD : AnonymousPercentTimeInCAS : AnonymousPercentTimeInMailboxRPC : EWSMaxConcurrency : 10 EWSPercentTimeInAD : 50 EWSPercentTimeInCAS : 90 EWSPercentTimeInMailboxRPC : 60 EWSMaxSubscriptions : 5000 EWSFastSearchTimeoutInSeconds : 60 EWSFindCountLimit : 1000 IMAPMaxConcurrency : IMAPPercentTimeInAD : IMAPPercentTimeInCAS : IMAPPercentTimeInMailboxRPC : OWAMaxConcurrency : 5 OWAPercentTimeInAD : 30 OWAPercentTimeInCAS : 150 OWAPercentTimeInMailboxRPC : 150 PowerShellMaxConcurrency : 18 PowerShellMaxTenantConcurrency : PowerShellMaxCmdlets : PowerShellMaxCmdletsTimePeriod : ExchangeMaxCmdlets : PowerShellMaxCmdletQueueDepth : PowerShellMaxDestructiveCmdlets : PowerShellMaxDestructiveCmdletsTimePeriod : RCAMaxConcurrency : RCAPercentTimeInAD : RCAPercentTimeInCAS : RCAPercentTimeInMailboxRPC : CPAMaxConcurrency : 20 CPAPercentTimeInCAS : 205 CPAPercentTimeInMailboxRPC : 200 MessageRateLimit : RecipientRateLimit : ForwardeeLimit : CPUStartPercent : 75 AdminDisplayName : |
SymantecEWSRestoreThrottlingPolicy has unlimited
The Throttling Policy from Symantec Backup Exec has a value of $null (Unlimited Powershell)
You should also check WIM interface:
winrm get winrm/config/winrs
Change with:
winrm set winrm/config/winrs @{MaxShellsPerUser=”25″}
winrm set winrm/config/winrs @{MaxConcurrentUsers=”25″}
Change in Powershell:
Get-ThrottlingPolicy | Set-ThrottlingPolicy -powershellmaxconcurrency 25
Please also see:
https://www.butsch.ch/post/Exchange-Error-you-get-while-you-open-the-EMC-GUI-Console.aspx