We had a perfectly function Exchange 2010 environment (over 1 year) but now we are unable to start the EMC or EMS from any account with administrative rights. The error returned does not reference any HTTP problems, and I have validated WinRM and checked and test the remote management functions. I have followed all the suggestions in the Articles for troubleshooting EMC and EMS startup issues. None seem to apply and all the items that are referenced check out correctly. I have also run EMTshooter and it produces the same output as opening the EMS.
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.
Checking IIS Service...
Checking the Exchange Install Path variable...
Checking the Powershell Virtual Directory...
Checking the Powershell vdir SSL setting...
Checking the Powershell vdir path setting...
Checking HTTP Port 80...
Checking HTTP Port 80 Host Name...
Testing for errors...
VERBOSE: Connecting to exchange.network.Local
Object reference not set to an instance of an object.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], RemoteException
+ FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:
exchange.network.Local
Failed to connect to any Exchange Server in the current site.
Problem found:
Looking for error...
Unknown Error
After each error is resolved, close this window and re-run the tool to check for additional problems.
All other functions are working perfectly - users can send and receive messages, OWA works, ActiveSync is functional and everything is fine. As I mentioned this is a production environment and has been running for over 1 year with out any issues