Monday, January 17, 2011

RESOLVED: 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 Z milliseconds.

I did some digging around for this one and found a few crafty articles about adjusting throttling policies using PowerShell and making changes through ADSIEdit (http://reidablog.blogspot.com/). However, none of these seemed to fix my issue.

We had a newly built Exchange 2010 SP1 server which was ready to go into production but kept throwing the error when attempting to use PowerShell. Two other servers appeared to be running fine.

The server had recently received a new SSL certificate using the Exchange 2010 certificate provisioning and assignment process in the GUI. Unfortunately the IIS service hadn't been restarted yet and the URL used for remote PowerShell was using a certificate which wasn't trusted or valid anymore.

A quick "IISRESET" on the server resulted in my fix.

Cheers!

175 comments:

  1. Thank you, that helped me alot to quickly fix my problem. Certificates are not really the first thing I would have thinked about.
    Erich

    ReplyDelete
  2. It helped me spot on. I was wondering what to do and no other site gave me this quick fix.

    ReplyDelete
  3. Excellent! Thank you, that did the trick! :)

    ReplyDelete
  4. Cool Beans! Fixed it for me too. Thanks.

    ReplyDelete
  5. Oh wow, that worked like a charm. I am surprised it was something that easy. Thank you!

    ReplyDelete
  6. Sweet! That command did the trick indeed! =)

    ReplyDelete
  7. Man you're the greatest, my woes ended in seconds - stay sharp

    ReplyDelete
  8. Fixed our issues as well, and enabled us to get our TSM backups running again.

    ReplyDelete
  9. Superb, no warning in the management tool when you change the certificate, Boo to microsoft yea to Jason Shave

    ReplyDelete
  10. Worked like a charm!!!!!! Awesome post dude!

    ReplyDelete
  11. Solved. Thanks a lot!

    ReplyDelete
  12. Perfect. IISRESET, who would have believed it?

    ReplyDelete
  13. Worked perfectly, thank you!

    ReplyDelete
  14. You are a scholar and a gentlemen. That worked perfectly. Thanks.

    ReplyDelete
  15. Sweet! That worked right away. Thanks!

    ReplyDelete
  16. Worked great here! Thanks

    ReplyDelete
  17. A scholar and a gentleman indeed! Many thanks.

    ReplyDelete
  18. Thanks! Worked great.

    ReplyDelete
  19. Yep, that worked for me too. Thanks!

    ReplyDelete
  20. Dang...I'm seeing it on my HT servers. When do IISReset \noforce, I get
    C:\Windows\system32>iisreset \noforce

    The RPC server is unavailable.
    C:\Windows\system32>

    ReplyDelete
  21. Another happy camper! It worked.

    Thank you for posting this!

    ReplyDelete
  22. Worked!! Thanks.

    ReplyDelete
  23. Saved us a call to MS Support.
    Thanks!!!

    ReplyDelete
  24. Thanks it worked just fine

    ReplyDelete
  25. Excellent. Perfect.

    ReplyDelete
  26. Wow...what a trick

    ReplyDelete
  27. Also for me too. You are a legend!!! Thanks!!

    ReplyDelete
  28. Brilliant! Absolutely brilliant! Thank you very much, quick-and-easy solution to a not-so-obvious error...

    -Cheers

    ReplyDelete
  29. Adding my thanks as well, fixed it right up. Nice and simple!

    ReplyDelete
  30. Yes! It worked! Thanks, you're the best!

    ReplyDelete
  31. Saved me a headache, thank you for sharing!

    ReplyDelete
  32. It worked. Thank you very very much.

    ReplyDelete
  33. Solved my issue very fast... thanks!

    ReplyDelete
  34. yep that fixed it. you the man now dowg thank you.

    ReplyDelete
  35. Worked for me as well. Thank you much for posting!

    ReplyDelete
  36. Thank you - I was about to open a case with Microsoft.

    ReplyDelete
  37. Another Exchange box fixed - thank you! Didn't think 2010 was so reliant on IIS like older Exchange systems...

    ReplyDelete
  38. Just wonderful! Thanks a lot!

    ReplyDelete
  39. Quick fix. Thanks!

    ReplyDelete
  40. Jason Shave is the man! Thanks, dude.

    Marco Alcala
    www.alcalaconsulting.com

    ReplyDelete
  41. simple and easy, thanks

    ReplyDelete
  42. Phew - thanks a mil

    ReplyDelete
  43. Thanks. Didn't know the solution was that simple. Cheers!

    Jenne, Netherlands

    ReplyDelete
  44. You made a simple solution to what looked like a significant problem. We had to do a restore of the system state about a month ago, thought it was related, happy to know it is not.

    ReplyDelete
  45. Awesome, that worked for me, too!
    Thanks!

    ReplyDelete
  46. Worked like a charm, cheers!

    ReplyDelete
  47. Thanks,

    It Worked WOW...

    Cheers

    ReplyDelete
  48. Worked for me. Thanks for the quick fix.

    ReplyDelete
  49. Worked for us too. Thank you so much.

    ReplyDelete
  50. thanks for doing the legwork! 5 second google and fix, preciate it

    ReplyDelete
  51. Thank you for posting, it works!

    ReplyDelete
  52. Worked for me too! Thanks !!!

    ReplyDelete
  53. hallelujah! a solution that actually worked
    many thanks

    ReplyDelete
  54. Worked for me too! You are the best!

    ReplyDelete
  55. Worked for me too. Perfect. Thanks,

    ReplyDelete
  56. you are a BLOODY champion! without this post, i would have spent hours. but took me 5 mins to get this issue fixed for the client just before Christmas break!

    ReplyDelete
  57. That's just plain awesome. Worked for me, and I didn't recently install a certificate but figured no harm trying it.

    ReplyDelete
  58. how do you run the iisreset command to do the quick fix for exchange 2010?

    ReplyDelete
  59. Awesome!!! You're the best!

    ReplyDelete
  60. JCM - It took me ages to find this article and seconds to fix.

    Well done pal - Virtual Beer-o-clock

    ReplyDelete
  61. Thats worked like a charm!!!

    ReplyDelete
  62. Great!! KUDOS!!... thanks for sharing this fix. worked perfect on my server!

    thanks!

    ReplyDelete
  63. ... Thanks Jason, It works like a charm, before i do iisreset, i see store.exe on 25 GB memory, and w3wp.exe on 6GB memory, after iisreset store.exe going down to 19 GB and w3wp.exe on 833 MB ...

    ReplyDelete
  64. Wow, thank you very much. Never had a fix work so well and quickly.

    ReplyDelete
  65. Thank you so much

    ReplyDelete
  66. The trusty old iisreset - works every time!

    ReplyDelete
  67. worked for me. Thank you very much. You are awsome dude
    ihsan y.

    ReplyDelete
  68. Worked here as well. However this issue seems to represent itself often. Is there any type of permanent fix?
    Thank you Jason.

    ReplyDelete
  69. Thanks a Lot. Sweet, simple, fast fix.

    ReplyDelete
  70. That did the trick! Thanks for taking the time to post this!!!!

    ReplyDelete
  71. Works like a charm!! Thanks

    ReplyDelete
  72. Good Work. Works like a charm.

    ReplyDelete
  73. Perfect fix to a Sunday morning. Thanks.

    ReplyDelete
  74. Darn, I usually resolved the issue by rebooting the entire server :(((

    THANK YOU FOR EXISTING ;)

    ReplyDelete
  75. Awesome, worked perfectly!

    ReplyDelete
  76. Poifect! - What a champ!

    ReplyDelete
  77. Thank you, that worked incredibly well ! You just shaved my day :)

    ReplyDelete
  78. Nice work, thanks!

    ReplyDelete
  79. What would the world be like without Google and the good Samaritans :)

    Thanks :)

    ReplyDelete
  80. Wonderful! Worked like a charm, thanks a lot!

    ReplyDelete
  81. Awesome...Thanks a lot.

    ReplyDelete
  82. That worked thanks, However the problem does come back and would have to manually do an IISRESET again. Need a more permanent solution.

    ReplyDelete
  83. As everyone else has said... Worked perfectly!! Thanks very much

    ReplyDelete
  84. To simple to belive, but it works, thanks:)

    ReplyDelete
  85. As if you haven't heard this enough, but... Excellent. Thanks!

    ReplyDelete
  86. Worked here as well. Thanks!

    ReplyDelete
  87. Awesome! Worked for me too! Thanks!!

    ReplyDelete
  88. Clever chap! Never expected it to be that...

    ReplyDelete
  89. In the middle of the bullseye!
    Thanks a lot!

    ReplyDelete
  90. Your solution continues to help us! Great job!

    ReplyDelete
  91. Worked for me - pobably saved me hours of troubleshooting!
    Thanks!

    ReplyDelete
  92. Spent about an hour of researching and attempting different remedies found online and I simply needed to run this!? You are much appreciated, sir.

    Thank you!

    ReplyDelete
  93. +1. Saved me a lot of time.

    ReplyDelete
  94. Ditto, became nervous there for a second but this took care of it perfectly. Thanks a bunch

    ReplyDelete
  95. Thank you for this help!

    ReplyDelete
  96. Good Fix Big Dog

    ReplyDelete
  97. Another thumbs-up from Colorado. Thanks for posting that.

    ReplyDelete
  98. You're a * STAR
    Thank you

    ReplyDelete
  99. THANK YOU!!!!!!!!

    ReplyDelete
  100. Jason you are a genius, THANK YOU

    ReplyDelete
  101. Good show!!! Helped me out with the same error. Thank you for sharing.

    ReplyDelete
  102. Kudos... saved me!

    ReplyDelete
  103. How Simple....Thanx. Petr

    ReplyDelete
  104. ------- Really? huh. iisreset. Done. Fixed. Ok off to get some coffee. Thank you Jason.

    ReplyDelete
  105. Thank you very much, you saved me. Mike

    ReplyDelete
  106. Years Later and it still helps

    ReplyDelete
  107. It worked for us too! Thanks!

    ReplyDelete
  108. Thanks a lot, this worked for me.
    I installed EMTshooter but it can't fix this error. Search for the error message and found your post.
    IISRESET fixed it in few seconds.

    ReplyDelete
  109. Can't believe that worked! Incredible Scenes! Thanks for this post :-)

    ReplyDelete
  110. Thank you very much! That also fixed my problem!

    ReplyDelete
  111. Thanks, IISRESET fixed the issue

    ReplyDelete
  112. Works for me..thanks for sharing this info :)

    ReplyDelete
  113. awesome thanks, saved a server reboot

    ReplyDelete
  114. Just piling on the appreciation. THANK YOU!

    ReplyDelete
  115. worked like a charm, saved much head scratching!

    ReplyDelete
  116. Yeeessss!! Thanks a bunch! Worked for me! :)

    ReplyDelete
  117. Worked like a charm. Thank you.

    ReplyDelete
  118. Worked for me also, thanks!

    ReplyDelete
  119. Worked for me today, many thanks IAB

    ReplyDelete
  120. Worked perfectly today thanks!

    ReplyDelete
  121. Huge tip. Thank you!

    ReplyDelete
  122. That was easy! Thanks for the info!

    ReplyDelete
  123. Fantastic, thank you, saves on a server reboot!

    ReplyDelete
  124. Worked perfectly.. thanks

    ReplyDelete
  125. Good tip - worked like a treat. Thanks!

    ReplyDelete
  126. excellent mate. good find. thanks!

    ReplyDelete
  127. Fixed my issue, thanks!

    ReplyDelete
  128. Fixed .... Thank You !!!!!!

    ReplyDelete
  129. Thanks for this. Worked a dream (and saved me from pulling more hair out).

    ReplyDelete
  130. Perfect! So glad I found this first.

    ReplyDelete
  131. Woohooo! Thanks!

    ReplyDelete
  132. Thanks! Perfect!

    ReplyDelete
  133. Four years later and the solution still worked. Thanks a lot Jason.

    ReplyDelete
  134. saved my day :D

    ReplyDelete
  135. Hope your not tired of hearing it but good post sorted it our for me also..Thanks

    ReplyDelete
  136. Worked for me. Can I buy you your favorite adult beverage?

    ReplyDelete
  137. Awesome, it worked for me as well. Thanks a bunch for the great tip.

    ReplyDelete
  138. I guess this still happened sometimes, it was not a certificate issue but the W3WP service was not stoppable. So taskmanager and closing down w3wp proces, start world wide webservice and it worked again.

    You got me on the right track.

    ReplyDelete
  139. Thanks, it worked for me too.

    ReplyDelete
  140. Alexis (Argentina)June 24, 2016 at 7:55 AM

    Gracias!!

    ReplyDelete
  141. Thank you for the tips. It works!

    ReplyDelete
  142. Thank you !!!!!
    I didn't change any certificates, nothing, just get this error, restart IIS - all fine !!!

    ReplyDelete
  143. Not had this problem before, but worked a treat - Thank you

    ReplyDelete
  144. This is the best solution that I found. Many others just suggested you to do things that you don't actually need it. Great job!!! Can't thanks you enough.

    ReplyDelete