EMC "selector value" error - Exchange 2010 on SBS 2011

Configuration: SBS 2011 Standard running Exchange 2010 with all MS updates installed.

Until recently I could open Exchange Management Console (EMC) when logged in as Domain\Administrator and everything was fine.

Currently I get the message:-

Starting a command on remote server failed with the following error message : The Windows Remote Shell cannot process the request; the selector value <SID> specified in the request was not found.

Searching on the web suggests that this is a problem with Windows Remote Management but I have:-
a) winrm quickconfig   - this returns no problems
b) checked the kerberos settings in default web site - powershell - modules and that's also fine
c) read this http://www.arconi.com/index.php/blog/item/exchange-2010-sp1-or-sp2-trouble-with-the-virtual-directory-powershell-already-exists and discovered that in IIS - default web site I have a virtual folder called PowerShell and one called PowerShell-Proxy . I don't know why I have the Proxy or whether it should even be there!

I've looked at the various event logs and I get a:-

MSExchangePowerShellAppPool exceeded time limites event ID 5013 but don't know if this is related.

The reason I discovered the EMC issue was because I need to renew a SSL certificate that expires in 4 days and I keep getting the "command on remote server failed" message.
Marcus NTechnical SpecialistAsked:
Who is Participating?
 
Marcus NTechnical SpecialistAuthor Commented:
OK, after a lot of searching I have fixed this myself. This article was a great help;

http://blogs.technet.com/b/jonjor/archive/2009/01/09/winrm-windows-remote-management-troubleshooting.aspx

So, this is the solution.
1) Open "Windows Firewall with Advanced Security"
2) Select "Inbound Rules"
3) Find the rule "Windows Remote Management - Compatibility Mode (HTTP-In)" and enable it.

Problem solved.

There's probably another way to do this that involves the default port 5985 somewhere in the Exchange Console settings, but I couldn't find it; probably something to do with "Tools - Remote Connectivity Analyzer" but I couldn't find any way to sort that out.
0
 
Sanjay SantokiCommented:
Hello,

Please make sure IPv6 is enabled which is required as per Microsoft even though it is not used in your network.

Also, You can try reinsalling WinRM.

Regards,
Sanjay Santoki
0
 
Marcus NTechnical SpecialistAuthor Commented:
IPv6 is enabled.

How do I reinstall WinRM? It's not in "control panel - programmes".

There is a folder %systemroot%\system32\winrm\0409 containing 1 file winrm.ini
0
 
Marcus NTechnical SpecialistAuthor Commented:
I had no real help and it took me a long time to track down the source of the problem which I have now tested and applied. I can say it fixes the problem completely.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.