Situation
Opening the Exchange Management Shell (EMS) on the server fails to connect to the local server with this error:
Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
Nice, huh? Looking at the event log gave me an RBAC error and a a few others as shown…
(Process w3wp.exe, PID 3244) "RBAC authorization is unavailable due to the transient error: The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via RPC. Error 0x5."
Process w3wp.exe (PID=3244). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 5 (Error 0x5 (Access is denied) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.
Process w3wp.exe (PID=3244). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 5 (Error 0x5 (Access is denied) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.
What changed over the last week? E2010 SP2 and RU1 had been run into the environment – but nothing else.
This was very frustrating because all the “normal” fixes to this did not work. WinRM extensions, Kerberos auth on the powershell vdir, rebooting, you name it, I looked at it. Nada.
The Fix
On a whim, while checking the PowerShell virtual directory path, and comparing a working server to this non-functioning server, I looked at the application pool…oh &%*!. How did it get that way? Four hours of chasing my tail. Four hours of my life I cannot get back.
My only thought is that SP2 or SP2 RU1 borked that setting for some bizarre reason. Here is a nice screen shot of what it was…
![clip_image002[5]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDbek5QaD_-VQXs7CV9kDh5BjriGhmjBNiesQEvnmVPuwYN3h1d9ZF6mOmKwxGjynMpi4jTvszVR0F2nj_tpNI3S6LRUgFhaxCmD2FKBdSJwr6jrtGI1q2cAPmF2NJJOIGwn4KAjM7ZiLI/s1600-h/clip_image002%25255B5%25255D%25255B3%25255D.jpg "clip_image002[5]")
…and what it should be:
YMMV
2 comments:
Amazing. I had the EXACT SAME PROBLEM and this fixed it by setting the AppPool soccertly as explained here! I was pulling my hair out as I tried all of the other "fixes" and non of them worked. This was an issue caused by SP2.
Amazing! This worked for me as well by setting the AppPool to powershell. I had tried all of the other fixes and nothing worked. This is an issue with SP2.
Post a Comment