troubleshooting Question

SBS2011 Can't connect to EMC/EMS

Avatar of browningit
browningitFlag for Canada asked on
27 Comments2 Solutions602 ViewsLast Modified:
Hi all,

I've been arguing with a server that I am assisting someone in fixing for a few hours now - and am nearly done fixing most of the issues - but the primary root of the problems still remains.  I can't launch the EMC or EMS, and EMShooter tells me the same thing over and over, with no recourse to resolve.  I've been over all the threads for SBS 2011 and Exchange 2010 on the topic, reviewed it all, and it just doesn't go anywhere.  There is one thing about the solution steps that is bothering me, and I am not sure it is relevant:

"The Exchange Management Troubleshooter indentified a problem that can be caused by several issues:

1. If the WSMan module entry is missing from the global modules section of the
C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:

           <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.

To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory.  Confirm that the WSMan entry exists in the Global Section of the ApplicationHost.config file as shown above.

2. Remote PowerShell uses Kerberos to authenticate the user connecting.  IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to \Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory.  The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.

3. The Path of the Powershell virtual directory has been modified.  The PowerShell virtual directory must point to the

"\Exchange Server\v14\ClientAccess\PowerShell"
The bold I have outlined above doesn't make sense.  I've reviewed everything else here and verified that all is fine, but still I can't get into EMS EMC.

Let me know if you have some clarification, or other ideas.  Thanks!

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 2 Answers and 27 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 27 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros