Hi,

Wondering if anyone can give some advice on an error I'm getting when trying to open EMC on my Exchange 2010 server (simple environment - running Windows 2008 R2 on Exchange...... 1 exchange 2010 server and two Windows 2008 domain controllers). 

The error I'm getting is the following:

Exchange 2010 EMC 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. 

I discovered my backup domain controller had gone down for some reason, but all it required was me to turn the power back on and the Backup DC booted up just fine. While it was down, all the other services on Exchange were working just fine.  There are no client issues and the server seems to be operating without any problems.  The only issue is opening EMC and getting the error above.

I waited a few hours after the backup domain controller was booted up to try opening the EMC, but am still getting the same error message.  The only event log I can find on it is in the application log "Event ID 1053 Source: MSFTESQL-Exchange - The system exception c0000005 was raised at 000007EFDE8BC989. Stack: "

I've done some searches and found various possiblities, but haven't tried anything yet.   I'm hopeful it's a simple issue to resolve.

Does anyone have any thoughts on how to resolve this?

Thanks!

Terry

Hi,

It is know issue when your cas server is down . Normmaly it should pick up another server in the site but it hasnt and if you are upgraded to sp2 ru4v2. it has been fixed.

Regards

Muthu

The CAS server is up and running and I don't think it ever went down (it's all on a single Exchange server).  The backup DC is the only thing that went down and it has been booted back up.  Everything should be operational, but I still can't access EMC.  I get the same message.

Thanks,

Terry

Hi

Did you try the solution on this KB

"Error message when you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "HTTP server error status (500)""

http://support.microsoft.com/kb/2027063

To resolve this problem, use one of the following methods:

• Make sure that the ExchangeInstallPath value is set correctly. To do this, open the System item in Control Panel, click Advanced system settings, and then click Environment variables on the Advanced tab. In the System variables box, locate the ExchangeInstallPath variable. The corresponding value for this variable should be C:\Program Files\Microsoft\Exchange Server\V14\.
• In IIS Manager, locate the entry for the PowerShell virtual directory under Default Web Site. Then, make sure that the entry points to the \Program Files\Microsoft\Exchange Server\v14\ClientAccess\PowerShell folder.

Cheers

If you have any feedback on our support, please click here

Hi,

Apologies for digging up this relatively old post but I am getting the same error message as the OP, however the solution is irrelevant / doesn't work and I can't fathom it out.

We have six Help Desk operatives - members of "Help Desk" and "View Only" RBAC. All Help Desk operatives  connect to a terminal server (2008 R2) where EMC and EMS is installed. The EMC works fine for all HD operatives, apart from one. When this operator clicks on anything under "Recipient Configuration" he gets the error described herein. It was fuly working until around early January 2014.

We don't see any event log errors on the Terminal Server or on Exchange 2010 pertaining to this fault.

Although he connectes to a terminal server, it is a one-off used for Exchange management only. It only uses local profiles. I have completely wiped his profile and seen the system build a new profile for him. As a test,
I added him to "Organisation Management" RBAC group and the issue went away - he was able to enumerate all users, when removed from "Organisation Management" and the problem returns.

When clicking on Recipient Configuration --> Mailbox, I see the PS cmdlet run is:

Get-Recipient -PropertySet ConsoleLargeSet -ResultSize '1000' -SortBy DisplayName -RecipientType 'UserMailbox'

He can connect to EMS and run this cmdlet without issue. I am at a loss as to where to go from here. Every Google results in checking the paths mentioned in KB2027063 (which are correct) or installing / reinstalling WinRM Extensions for IIS, which are fine, otherwise the issue would affect all users.

Any help would be gratefully received

Many thanks

Myself and an Exchange admin troubleshot this for 6 hours for one user. All permissions are good and all settings were good. Finally the only way that the issue was resolved was creating a new account for the user with same group memberships and everything. User was able to go about his work just fine after that.

R/S

Chase