Brian St. Marie - Sr. Systems Engineer
I ran into an interesting issue today with Exchange 2010. I needed to add a few user mailboxes to an Exchange server, but when I tried to open the Exchange Management Console, I was greeted with a rather startling error:
"The WS-Management service cannot process the request. The user load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least <large number> milliseconds."
I next tried to fire up the Exchange Management Shell and received the same error. Worrisome, but I hadn't heard any reports from users about email issues, so I knew it couldn't be anything too severe.
My initial thought that somehow the server was under attack and being subjected to a large number of requests from a foreigh host proved to be untrue. A bit of research turned up many different options for possible fixes, including registry modifications, IIS reconfigurations, and powershell commands to disable and remove SSL (see http://social.technet.microsoft.com/Forums/en/exchange2010/thread/4d396628-3867-4c95-9541-e0eb021e0135). One blog even hinted at ADSIEdits. However, the SSL issue tipped me off, as I had just recently renewed the SSL certificate on this server. This turned up a very helpful blog entry (http://jasonshave.blogspot.com/2011/01/resolved-ws-management-service-cannot.html) which suggested a simple IIS reset.
I opened a run prompt and ran 'iisreset /noforce', after which everything was back to normal. Just goes to show that even though an error can seem dire, the solution is often quite simple. It's always worth looking for the simple solution before getting too complicated and making a situation much worse than it already is.