locked
The WinRM client cannot process the request RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I launch emc on cas server and get 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."
    Then I access cas default web site by ip address and also get error web.
    Error HTTP Error 401.0 - Access Denied.
    Module kerbauth 
    Thursday, February 2, 2012 11:27 AM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Did you miss the sticky at the top of the forum :)

    http://social.technet.microsoft.com/Forums/en-GB/exchange2010/thread/51b9f958-0ed4-45d4-a0f4-b853f0ade2e2

    Thursday, February 2, 2012 11:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    can you tell me if you install exchange in physical or virtual server ?

    there are meny issue for this topic :

    1. IIS kerberos authentication : 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 C:\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, in IIS 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.

    2. version of powershell and WInRM used

    3. If you use a virtual instance, try to desactivate time synchronization with the physical Computer ( from HyperV management console for exemple ) and synchronize with your DC

    Thanks,

    Thursday, February 2, 2012 1:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please verify below informations:

    1 Removing WinRM feature and reinstalling.

    2 Rename the web.config file in location C:\inetpub\wwwroot

    3 Have you installed Microsoft Dynamics CRM 4. I?

    Also, please try these solutions:

    http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

    http://www.msexchangegeek.com/2010/12/17/the-winrm-client-cannot-process-the-request-the-content-type-is-absent-or-invalid/

     

    Rowen

    TechNet Community Support

    • Proposed as answer by Rowen-Xu Sunday, February 12, 2012 2:39 AM
    • Marked as answer by Rowen-Xu Monday, March 5, 2012 6:12 AM
    Friday, February 3, 2012 2:37 AM