Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 15005

The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer

$
0
0

I installed SSL certificate on my exchange server and enabled SSL on the default website, autodiscover, ecp, ews, owa, rpc, rpcwithcert and startedo receive follwong error when a user pointed to http://mail.mydomain.com.

403 - Forbidden: Access is denied.

You do not have permission to view this directory or page using the credentials that you supplied.

I came across an article http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/ to redirect http to https. It worked, users are now redirected to the https and no longer receive the 403 error.

Since then I am receiving the following error on EMC:

Initialization failed

The following error occurred when retrieving user information for 'domain\user':

Starting a command on 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.

I have tried the following but none of those have worked for me.

  • Install WinRM IIS Extension

  • winRM quickconfig

  • issreset /noforece

  • Downloaded EMTshooter which reports no errors (http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx)

  • Checked the environment variable ExchangeInstallPath – it is set correctly

  • Created a key in registry under HKLM\microsoft\Exchage\setup and added DWORD services with installation path of Exchange server

  • Checked settings mentioned in http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

  • Checked kerbauth module in powershell vdir – it set to native and entry type is local

  • Checked kerbauth module in Default Website – it does not exist there

  • Checked \ApplicationHost.config for the entry<globalModules>
    <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
    - It does exist in the file

  • Checked (Get-User <username>).RemotePowershellEnabled– User is enabled

  • Checked bindings in default website for HTTP. The binding parameters are correct

  • Checked Authentication under powershell vdir – All authentication types are disabled

  • Check winhttp proxy – It is set properly

Does anybody have any clue whats wrong?

PS: EMS connects without any errors but occasionally gives winRM error


Viewing all articles
Browse latest Browse all 15005

Trending Articles