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!
Monday, January 17, 2011
Subscribe to:
Post Comments (Atom)
Thank you, that helped me alot to quickly fix my problem. Certificates are not really the first thing I would have thinked about.
ReplyDeleteErich
It helped me spot on. I was wondering what to do and no other site gave me this quick fix.
ReplyDeleteExcellent! Thank you, that did the trick! :)
ReplyDeleteCool Beans! Fixed it for me too. Thanks.
ReplyDeleteOh wow, that worked like a charm. I am surprised it was something that easy. Thank you!
ReplyDeleteSweet! That command did the trick indeed! =)
ReplyDeleteMan you're the greatest, my woes ended in seconds - stay sharp
ReplyDeleteFixed our issues as well, and enabled us to get our TSM backups running again.
ReplyDeleteSuperb, no warning in the management tool when you change the certificate, Boo to microsoft yea to Jason Shave
ReplyDeleteWorked like a charm!!!!!! Awesome post dude!
ReplyDeleteSolved. Thanks a lot!
ReplyDeletePerfect. IISRESET, who would have believed it?
ReplyDeleteThat helped, thanks!
ReplyDeleteWorked perfectly, thank you!
ReplyDeleteWorked!! Thanks.
ReplyDeleteYou are a scholar and a gentlemen. That worked perfectly. Thanks.
ReplyDeleteSweet! That worked right away. Thanks!
ReplyDeleteWorked great here! Thanks
ReplyDeleteA scholar and a gentleman indeed! Many thanks.
ReplyDeleteThanks! Worked great.
ReplyDeleteYep, that worked for me too. Thanks!
ReplyDeleteDang...I'm seeing it on my HT servers. When do IISReset \noforce, I get
ReplyDeleteC:\Windows\system32>iisreset \noforce
The RPC server is unavailable.
C:\Windows\system32>
Thanks!
ReplyDeleteAwesome.
ReplyDeleteAnother happy camper! It worked.
ReplyDeleteThank you for posting this!
Word
ReplyDeleteWorked!! Thanks.
ReplyDeleteSaved us a call to MS Support.
ReplyDeleteThanks!!!
Thanks it worked just fine
ReplyDeleteExcellent. Perfect.
ReplyDeleteWow...what a trick
ReplyDeleteAlso for me too. You are a legend!!! Thanks!!
ReplyDeleteBrilliant! Absolutely brilliant! Thank you very much, quick-and-easy solution to a not-so-obvious error...
ReplyDelete-Cheers
Thx!
ReplyDeleteAdding my thanks as well, fixed it right up. Nice and simple!
ReplyDeleteYes! It worked! Thanks, you're the best!
ReplyDeleteSaved me a headache, thank you for sharing!
ReplyDeleteIt worked. Thank you very very much.
ReplyDeleteYou Da Man!
ReplyDeleteSolved my issue very fast... thanks!
ReplyDeleteyep that fixed it. you the man now dowg thank you.
ReplyDeleteWorked for me as well. Thank you much for posting!
ReplyDeleteThank you - I was about to open a case with Microsoft.
ReplyDeleteI love you
ReplyDeleteAnother Exchange box fixed - thank you! Didn't think 2010 was so reliant on IIS like older Exchange systems...
ReplyDeleteJust wonderful! Thanks a lot!
ReplyDeleteQuick fix. Thanks!
ReplyDeleteJason Shave is the man! Thanks, dude.
ReplyDeleteMarco Alcala
www.alcalaconsulting.com
simple and easy, thanks
ReplyDeletePhew - thanks a mil
ReplyDeleteThanks. Didn't know the solution was that simple. Cheers!
ReplyDeleteJenne, Netherlands
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.
ReplyDeleteAwesome, that worked for me, too!
ReplyDeleteThanks!
Worked like a charm, cheers!
ReplyDeleteThanks,
ReplyDeleteIt Worked WOW...
Cheers
BANG ON!
ReplyDeleteWorked for me. Thanks for the quick fix.
ReplyDeleteWorked for us too. Thank you so much.
ReplyDeletethanks for doing the legwork! 5 second google and fix, preciate it
ReplyDeleteThank you for posting, it works!
ReplyDeleteFixed our problem!!
ReplyDeleteWorked for me too! Thanks !!!
ReplyDeletehallelujah! a solution that actually worked
ReplyDeletemany thanks
Worked for me too! You are the best!
ReplyDeleteWorked for me too. Perfect. Thanks,
ReplyDeleteyou 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!
ReplyDeleteThat's just plain awesome. Worked for me, and I didn't recently install a certificate but figured no harm trying it.
ReplyDeletehow do you run the iisreset command to do the quick fix for exchange 2010?
ReplyDeleteYou da man!
ReplyDeleteAwesome!!! You're the best!
ReplyDeleteJCM - It took me ages to find this article and seconds to fix.
ReplyDeleteWell done pal - Virtual Beer-o-clock
Thats worked like a charm!!!
ReplyDeletePerfect, thanks!
ReplyDeleteGreat!! KUDOS!!... thanks for sharing this fix. worked perfect on my server!
ReplyDeletethanks!
... 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 ...
ReplyDeleteExcellent
ReplyDeleteThank you.
ReplyDeleteWow, thank you very much. Never had a fix work so well and quickly.
ReplyDeleteThank you so much
ReplyDeleteThe trusty old iisreset - works every time!
ReplyDelete