locked
EMC Error RRS feed

  • Question

  • Hi there.

    I have running Exchange 2010 sp2 and I got the 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. "

    It shows since I use the EMC to install a SSL certificate from a external CA. I should have used Import-ExchangeCertificate command but I used the EMC and I guess this is the cause.

    I tried to use EMC troubleshooter, WinRM troubleshooters, and stuff like http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx

    from other post but all are right and still doesn't work.

    I checked kerbauth.dll and wsman modules in IIS and in <global modules> section from applicationHost.config file in c:\windows\systerm32\inetsrv\config and it's ok too. Also checked both modules in IIS server section and is registered but not enabled, but enabled in PowerShell virtual directory from Default Web Site.

    So I guess all is well configured but not at all cause I'm still getting the error :(

    Any help would be appreciated.

    Best regards.

    Monday, July 30, 2012 10:41 AM

Answers

  • I answer myself. The problem was caused due a conflict with c:\inetpub\wwwroot\config.xml file and winRM. Once I've eliminated that file the issue solves itself.

    Regards.

    Thursday, August 9, 2012 7:49 AM

All replies

  • I've seen that error many times and it can be caused by all sorts of different things.  Search the Internet for the salient bits of the error message and you should find lits of suggestions.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Tuesday, July 31, 2012 4:58 AM
  • Hi

    Try the solution on below support link

    Error message when you try to start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The WinRM client... cannot determine the content type of the HTTP response from the destination computer"

    http://support.microsoft.com/kb/2028305

    Cheers


    Zi Feng

    TechNet Community Support

    Tuesday, July 31, 2012 8:29 AM
    Moderator
  • Hi. Thanks for you response, but I've checked that too :( Answered in bold.

    • The Kerbauth module is configured incorrectly in Internet Information Services (IIS) in one of the following ways:
      • The Kerbauth module is displayed as a Managed module instead of as a Native module. This module is as a Native Module
      • The Kerbauth module has been loaded on the Default website level (instead of, or in addition to, the PowerShell virtual directory). The module is loaded just in PowerShell virtual directory.
    • The user does not have Remote PowerShell Enabled status. (get-user <myuser>).remotepowershellenabled gets back $true. Try with other admins and neither login to EMC
    • The WSMan module entry is missing from the Global modules section of the ApplicationHost.config file that is in the following location: 

      C:\Windows\System32\Inetsrv\config\ApplicationHost.config 

      This causes the WSMan module to be displayed as a Managed module in the PowerShell virtual directory. It's displayed like as native module and it's registered in ApplicationHost.config file

    Wednesday, August 1, 2012 10:39 AM
  • Any news?
    Monday, August 6, 2012 8:06 AM
  • I answer myself. The problem was caused due a conflict with c:\inetpub\wwwroot\config.xml file and winRM. Once I've eliminated that file the issue solves itself.

    Regards.

    Thursday, August 9, 2012 7:49 AM