Exchange 2010 unable to access EMC or EMS

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Exchange 2010 unable to access EMC or EMS
Event ID 32784: The WS-Management service cannot process the request

Symptoms: When attempting open EMC, you may receive this message: "The WS-Management service cannot process the request. The system load quota of 1000 requests per 2 seconds has been exceeded" and can't navigate it.

2. Windows PowerShell Event Log contains the error presented when attempting to access Exchange Management.

Log Name: Microsoft-Windows-PowerShell/Operational
Source: Microsoft-Windows-PowerShell
Event ID: 32784

Computer: exch-cas02
Description:
Runspace Id: 2801cb15-e2f9-4049-9d32-5a26ad67f49a Pipeline Id: 00000000-0000-0000-0000-000000000000. 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 Help topic.

Case 1: In most cases, this issue is related to IIS. Try to start using IISRESET.

Case 2: Can you check and see if the "Default web site" is set to use Host Header and to use the IP address?
If that is the case, then set the "Default website" to All Unassigned and also remove the Host Header.
For access to the tools urgently, please install the 32 bit management tools in a 32 bit machine.

Case 3: Solution wich worked for me was:

1. make sure IIS WinRM extension is installed
2. open powershell and run command : WinRM Quickconfig
3. Open IIS go to Powershell virtual directory and check that SSL in disabled and authentification is set only to Anonymous
4. Open Windows powershell modules
5. run Remove-PowershellVirtualDirectory command
6. run New-PowershellVirtuallirectory command
7. IISreset

Case 4: •In the IIS Manager create a new Application for your default Website called: "PowerShell" and use the "MSExchangePowerShellAppPool". Point the physical path to: "C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell"
•Open the following file: "C:\Windows\System32\inetsrv\config\applicationHost.config" and add these 2 Lines in the "<globalModules>" Section:
<add name="WSMan" image="C:\Windows\System32\WsmSvc.dll" />
<add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll" />

•Go back to IIS Manager and open the Module Section within the PowerShell Website. Right Click and choose "Configure Native Modules". Add here your WSMan and kerbauth Module.
•Make sure that SSL required isn´t hooked in the SSL Options from the Powershell Website
•open powershell and run "WinRM Quickconfig"
•do a iisreset
After I´ve done this steps my Exchange Management Console and Shell worked fine again.

Case 5: After rebooting the server I was able to use EMC/EMS again.

Case 6: If you open multiple Exchange Management Consoles and/or remote PowerShell instances,you may receive this error. To check what the current WinRM/WinRS settings, run this from an administrative command line:
winrm get winrm/config/winrs

The output should look something like this:

AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 5
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 5

To raise the limits a little bit, run the following commands:
winrm set winrm/config/winrs @{MaxShellsPerUser="25"}
winrm set winrm/config/winrs @{MaxConcurrentUsers="25"}

The output should now look like this:

AllowRemoteShellAccess = true
IdleTimeout = 180000
MaxConcurrentUsers = 25
MaxShellRunTime = 2147483647
MaxProcessesPerShell = 15
MaxMemoryPerShellMB = 150
MaxShellsPerUser = 25
Or run this Powershell cmdlet:
Get-ThrottlingPolicy | Set-ThrottlingPolicy -powershellmaxconcurrency 25

Post your questions, comments, feedbacks and suggestions

Contact a consultant