The WinRM client cannot process the request….The content type is absent or invalid

One of my customers logged a case yesterday asking to fix their EMS issue on their only Exchange 2010 server. They were neither able to open the EMC on the server nor from a remote computer. The error that was shown in EMC was:

"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."

Of course I followed the Exchange Team’s article http://msexchangeteam.com/archive/2010/02/04/453946.aspx to fix the WinRM connectivity issues but it didn’t work unfortunately. After checking all permissions and settings on Powershell virtual directory, I downloaded and ran recently released EMTshooter.ps1 powershell script from http://msexchangeteam.com/archive/2010/12/07/457139.aspx but it wasn’t able to fix the problem either.

Another symptom that I noticed is when I double click the Modules in Powershell virtual directory, I get an error saying,

This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false". 

Config File \?C:Program FilesMicrosoftExchange ServerV14ClientAccessPowershellweb.config

After opening the web.config file and looking in the file carefully I noticed that the file has two environment variables used %ExchangeInstallDir% and %ExchangeInstallDirPath%. These variables are supposed to be registered in advanced system properties page of the operating system. In my case the physical path for %ExchangeInstallDirPath% was missing. This path should be the actual installation directory of your exchange server (Normally C:Program FilesMicrosoftExchange ServerV14)

Once you open system properties and create the missing environment variable %ExchangeInstallDir% or %ExchangeInstallDirPath% depending upon the situation you have and point the physical path to C:Program FilesMicrosoftExchange ServerV14 (Note the after directory V14) You should be able over come the error that EMS shows up.

I hope that helps Smile