Skip Ribbon Commands
Skip to main content

Xadean's Empirical Musing


Quick Launch

Xadean's Empirical Musing > Posts > Exchange Server 2013 Management Tools (EMS & EAC) Failing with Errors
November 05
Exchange Server 2013 Management Tools (EMS & EAC) Failing with Errors

Issue Experienced:

When attempting to launch Exchange Management Shell (EMS) and Exchange Admin Center (EAC), running into the following error messages respectively.

EMS Error #1:


Welcome to the Exchange Management Shell!


Full list of cmdlets: Get-Command

Only Exchange cmdlets: Get-ExCommand

Cmdlets that match a specific string: Help *<string>*

Get general help: Help

Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?

Exchange team blog: Get-ExBlog

Show full output for a command: <command> | Format-List


Show quick reference guide: QuickRef

Tip of the day #63:


Any cmdlet that accepts a size value lets you specify whether the integer value is in kilobytes (KB), megabytes (MB), gi

gabytes (GB), or terabytes (TB). For example:


Set-Mailbox "Kim Akers" -ProhibitSendQuota 200MB -UseDatabaseQuotaDefaults $False


VERBOSE: Connecting to

New-PSSession : [] Connecting to remote server failed with the

following error message : <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"


<html xmlns="">


<title>IIS 8.0 Detailed Error - 500.0 - Internal Server Error</title>

<style type="text/css">




.config_source code{font-size:.8em;color:#000000;}


ul,ol{margin:10px 0 10px 5px;}


fieldset{padding:0 15px 10px 15px;word-break:break-all;}

.summary-container fieldset{padding-bottom:5px;margin-top:4px;}{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}

legend{color:#333333;;margin:4px 0 8px -12px;_margin-top:0px;






h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;}

h4{font-size:1.2em;margin:10px 0 5px 0;

}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif;


}#content{margin:0 0 0 2%;position:relative;}


.content-container p{margin:0 0 10px 0;



}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF;

background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal;


}#server_version p{margin:5px 0;}

table{margin:4px 0 4px 0;width:100%;border:none;}

td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:normal;border:none;}


thead th{background-color:#ebebeb;width:25%;

}#details-right th{width:20%;}

table tr.alt td,table tr.alt th{}



.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;}






<div id="content">

<div class="content-container">

<h3>HTTP Error 500.0 - Internal Server Error</h3>

<h4>Module &quot;WSMan&quot; could not be found</h4>


<div class="content-container">

<fieldset><h4>Most likely causes:</h4>

<ul> <li>The module could not be found.</li> <li>IIS received the request; however, an internal error

occurred during the processing of the request. The root cause of this error depends on which module handles the

request and what was happening in the worker process when this error occurred.</li> <li>IIS was not able to access

the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.</li>

<li>IIS was not able to process configuration for the Web site or application.</li> <li>The authenticated user

does not have permission to use this DLL.</li> </ul>



<div class="content-container">

<fieldset><h4>Things you can try:</h4>

<ul> <li>Verify that the module name is not misspelled in the configuration/system.webServer/globalModules

config section. The error description may contain additional information to help you determine which module is causing

the error.</li> <li>Ensure that the NTFS permissions for the web.config file are correct and allow access to the

Web server's machine account.</li> <li>Check the event logs to see if any additional information was logged.</li>

<li>Verify the permissions for the DLL.</li> <li>Create a tracing rule to track failed requests for this HTTP

status code. For more information about creating a tracing rule for failed requests, click <a

href="">here</a>. </li> </ul>




<div class="content-container">

<fieldset><h4>Detailed Error Information:</h4>

<div id="details-left">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Module</th><td>&nbsp;&nbsp;&nbsp;IIS Web Core</td></tr>


<tr class="alt"><th>Handler</th><td>&nbsp;&nbsp;&nbsp;Not yet determined</td></tr>

<tr><th>Error Code</th><td>&nbsp;&nbsp;&nbsp;0x80070002</td></tr>




<div id="details-right">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Requested URL</th><td>&nbsp;&nbsp;&nbsp;




<tr><th>Physical Path</th><td>&nbsp;&nbsp;&nbsp;C:\Program Files\Microsoft\Exchange


<tr class="alt"><th>Logon Method</th><td>&nbsp;&nbsp;&nbsp;Not yet determined</td></tr>

<tr><th>Logon User</th><td>&nbsp;&nbsp;&nbsp;Not yet determined</td></tr>



<div class="clear"></div>





<div class="content-container">

<fieldset><h4>More Information:</h4>

This error means that there was a problem while processing the request. The request was received by the Web server,

but during processing a fatal error occurred, causing the 500 error.

<p><a href=";IIS70Error=500,0,0x80070002,9200">View more information


<p>Microsoft Knowledge Base Articles:</p>








Error occurred during the Kerberos reponse.

[Server=ExchSrvr, TimeStamp = 114/2018 23:28:18]

For more information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1

+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin


+ FullyQualifiedErrorId : -2144108173,PSSessionOpenFailed


EMS Error #2:

failed with the following error message: [ClientAccessServer=,BackEndServer=,RequestId=d89f6ed1-19

8b-4a00-9941-a08f1bb78c54,TimeStamp=11/5/2018 6:58:02 AM]

[AuthZRequestId=b2c5b4c3-edd9-410c-a7fe-af0499783858][FailureCategory=AuthZ-SetupVersionInformationCorruptException] Unable to determine the installed file version from the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine'. For more information, see the about_Remote_Troubleshooting Help topic.

At line:1 char:1


EAC Error #1 (occurs with EMS Error #2):

Connecting to remote server failed with the following error message : IIS 8.0 Detailed Error - 500.0 - Internal Server Error



EMS Error #1 occurs because the WS-Management (WSMan) module is not registered / loaded in IIS.


EMS Error #2 and EAC Error #1 occurs because Windows PowerShell version 2.0 is not installed.



To resolve EMS Error #1 follow these steps.

  1. Open IIS and navigate to the Default Web Site.
  2. In the control pane, click on Modules.
  3. WSMan should not be found in the enabled modules list.
  4. Click on Configure Native Modules in the action pane.
  5. Verify that WSMan is listed there without a check in the box next to it.
    1. If WSMan is not listed, go to step 10.
  6. Navigate to PowerShell virtual directory under Default Web Site.
  7. Click on Modules in the control pane.
  8. Verify WSMan is not in the list of enabled modules.
  9. Click on Configure Native Modules in the action pane. Verify that WSMan is listed without a check in the box next to it.
  10. If WSMan does not appear in the list, click on the Server's Name in the left navigation pane and then click on Modules in the control pane.
  11. Click on Configure Native Modules in the action pane.
  12. Click on the Register button.
  13. Enter "WSMan" in the Name field and "%windir%\system32\wsmsvc.dll" (both entries without the quotation marks). Click OK button to save and register.
  14. WSMan should now appear in the list of native modules without a check in the box next to it.
  15. Open a Command Prompt (w/ administrator privileges) and execute IISRESET /noforce command.

Error EMS #1 should now be resolved when you retry performing the action.


To resolve EMS Error #2 and EAC Error #1, perform the following steps to install Windows PowerShell version 2.0.

  1. Open Server Manager.
  2. Click on Manage and then select Add Roles and Features.
  3. Click next a few times in the wizard until you reach Select Features screen.
  4. Expand Windows PowerShell selection and check the box next to Windows PowerShell 2.0 Engine and then keep clicking next until you see an install button.
  5. Click install and wait until the operation completes.
  6. Reboot the server.

When you launch EMS or EAC, you should be able to get into both tools without any issue at this point.


Re: Exchange Server 2013 Management Tools (EMS & EAC) Failing with Errors

 on 10/8/2019 9:12 AM

nike outlet Yeezy Shoes Yeezy Adidas Yeezy Nike UK Nike outlet Nike Nike Outlet Nike Outlet Nike Store Nike Store Louis Vuitton Louis Vuitton Online Shop Adidas Yeezy Yeezy Shoes Adidas Yeezy Yeezy Slides Yeezy Supply Golden Goose Golden Goose Sneakers Air Jordan 1 Jordan 1 Jordan Shoes Jordan 1 Air Jordan 1 Jordan 1 Yeezy slides Yeezy Yeezys Adidas Yeezy Ray Ban Sunglasses Ray Ban Glasses 天目茶碗 曜変天目茶碗 曜変天目 Nike Shoes Jordan 4S Jordan 4 Nike Outle Jordan 1S Yeezy Shoes Yeezy Supply Yeezy Slides Coco Chanel Chanel Chanel Handbags Coco Chanel Chanel Chanel Handbags Chanel West Coast gucci Yeezy 350 Yeezy Slides Yeezy Slides Yeezy Slides Yeezy Yeezy Supply Yeezy Supply Yeezy Shoes Yeezy Shoes Nike Store Nike Shoes Nike Outlet Nike Shoes Ray Ban Sunglasses Ray ban Sale Coach Coach outlet Gucci Outlet Louis Vuitton Outlet Louis Vuitton Louis Vuitton Handbags Louis Vuitton Outlet Louis Vuitton Rolex Watches Rolex Watches Rolex Watches Rolex Rolex Rolex North Face Outlet North Face The North Face Nike Shoes Nike Outlet Store Yeezy Slides Yeezy Shoes Yeezy Supply Yeezy Shoes Yeezy Shoes Burberry Sale Burberry Outlet Yeezy Supply Pandora Necklace Michael Kors Outlet Michael Kors Off White Shoes Moncler Outlet Moncler Factory Moncler Vest Moncler Coat Burberry Outlet Online Michael Kors Outlet Yeezy Slides Yeezy Slides Yeezy Slides Yeezy Slides Yeezy Slides Yeezy Supply Nike Shoes
 on 6/18/2022 12:05 PM

Add Comment


Body *