Compartir a través de

getting an error when you open EMC / EMS

  • Artículo

some times after you install service pack or update roll up for exchange 2010 you find that EMC / EMS are not working with below error

Connecting to remote server failed with the following error
message: The WinRM client cannot process the request. It cannot determine the
content type of the HTTP response from the destination computer. The content
type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.

 

looking at the application log we can see the below warning

 

 Log Name:      Application

Source:        ASP.NET
2.0.50727.0

Date:         
3/11/2012 11:22:04 AM

Event ID:      1310

Task Category: Web Event

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:     
ABC.XYZ.LOCAL

Description:

Event code: 3008

Event message: A configuration error has occurred.

Event time: 3/11/2012 11:22:04 AM

Event time (UTC): 3/11/2012 8:22:04 AM

Event ID: c21330b3c7e64e37938fefc93278b3b0

Event sequence: 2

Event occurrence: 2

Event detail code: 0

 

Application information:

    Application
domain: /LM/W3SVC/1/ROOT/PowerShell-1-129759272693526091

    Trust level: Full

    Application
Virtual Path: /PowerShell

    Application Path:
D:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell\

    Machine name:
ABC

 

Process information:

    Process ID: 7192

    Process name:
w3wp.exe

    Account name: NT
AUTHORITY\SYSTEM

 

Exception information:

    Exception type:
ConfigurationErrorsException

    Exception message:
Could not load file or assembly
'Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The system cannot find the file specified. (D:\Program Files\Microsoft\Exchange
Server\V14\ClientAccess\PowerShell\web.config line 42)

 

Request information:

    Request URL:
https://ABC.XYZ.LOCAL/PowerShell?PSVersion=2.0

    Request path:
/PowerShell

   

    User: 

    Is authenticated:
False

    Authentication
Type: 

    Thread account
name: NT AUTHORITY\SYSTEM

 

Thread information:

    Thread ID: 7

    Thread account
name: NT AUTHORITY\SYSTEM

    Is impersonating:
False

    Stack trace:    at
System.Web.Configuration.ConfigUtil.GetType(String typeName, String
propertyName, ConfigurationElement configElement, XmlNode node, Boolean
checkAptcaBit, Boolean ignoreCase)

   at
System.Web.Configuration.Common.ModulesEntry..ctor(String

 

looking at the above warning looks like something missed up in the web.config under power shell directory

 

if we edit the web.config we can see a variable called %ExchangeInstallDir% but that variable doesn't exist in the environment variable path, even after we add it still the issue is the same

so what i did here is replace this variable with the physical path as below

 

open web.config

Replace all "file:///%ExchangeInstallDir%" with "file:///D:\Program Files\Microsoft\Exchange Server\" where D is the drive where Exchange is installed

Save the file

iisreset

 

now EMC and EMS should open properly

Comments

  • Anonymous
    January 01, 2003
    its my pleasure

  • Anonymous
    January 01, 2003
    you are most welcome, im very happy to help

  • Anonymous
    May 10, 2013
    Thank you very much, it worked for me i was working on this error 2 days.

  • Anonymous
    June 02, 2013
    THANK YOU! 6hrs of reading the same suggestions over and over again with no success.. This one fixed it!

  • Anonymous
    August 19, 2013
    Thank U! I was close to givin up until I found this. Worked!

  • Anonymous
    November 27, 2013
    It worked, I must say I skeptical but now it leads me to think you could probably also reset the environment variable. Thanks

  • Anonymous
    December 09, 2013
    Thanks, after trying everything else and failing this worked!

  • Anonymous
    December 09, 2013
    my pleasure to help

  • Anonymous
    February 20, 2014
    Thank You.. Replacing the web.config dir path helped me resolve the issue.

  • Anonymous
    November 18, 2014
    Thank you this works for me after a week of troubling on SP3...thank you again!

  • Anonymous
    December 27, 2014
    This did the trick for me and I had been working on this for days and days!!!!!

  • Anonymous
    April 24, 2018
    Your method of describing everything in this piece of writing is genuinely fastidious, every one can effortlessly know it, Thanks a lot.