WinRM cannot determine the content type of the HTTP response from the destination computer!!!

All replies

• 

  

  0

  Sign in to vote

  I need help regarding an error i have on exchange server 2010.

  I installed a Windows Server 2008R2 server, created the domain etc. The server has all the updates etc installed. Then installed SQL Server 2008R2. Then installed Exchange Server 2010 SP1. I had to download and install various patches etc as pointed out by Microsoft to be able to install Exchange. At this point everything was working fine and i could start the Exchange Management Console and everything was fine.

  
  

  I then installed Microsoft Dynamics CRM 4. I went ahead and specified the default web site for it. It installed fine and i can actually see and connect to the dynamics CRM website.

  
  

  Since then i could not connect to Exchange using the Exchange Management Console. It kept giving an error that unable to initialize consoleinitialize.ps1.

  
  

  After a LOT of troubleshooting i found that the application pools for some reason were pointing to wrong application pools. So i set the application pools to what i think should be for example for ECP i set ECPappool etc. Also Dynamics CRM had changed the name of the Default Web Site to Microsoft Dynamics CRM, so i renamed the website back to Default Web Site.

  
  

  What i do not know is what specs the application pools should all be set to? i just chose the defaults like integrated, local system, .net v2 etc. After that when starting Exchange Management Console, i do not get the consoleinitialize.ps1 error anymore but get another error as follows:

  
  

  "The attempt to connect to http://g1-server.g1.local/Powershell using Kerberos authentication failed.

  
  

  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 troubleshooting see the about_Remote_Troubleshooting Help topic."

  
  

  When i try to type "http://g1-server/ecp" it waits for a while then asks for authentication and after typing the administrator username and password takes a long time and then just times out. 

  
  

  When i try to type "http://g1-server/owa" it gives a 500.22 Internal Server Error - An ASP.net setting has been detected that does not apply in Integrated managed pipeline mode.

  
  

  Someone said on Technet forum post that removing and re-adding WinRM IIS extension solves the issue and i have done that as well but its done nothing and the problem remains.

  
  

  I have tried everything and looked everywhere, even posted a previous post on Microsoft Technet forum but am not getting a response and unable to resolve this problem.

  
  

  Can anyone please help me?

  
  

  Thanking you,

  Rashid Khan

  I found the solution courtesy of "msillers" !

  
  

  Resolved this by renaming (as opposed to deleting) the web.config file in c:\intepub\wwwroot directory then issuing the iisreset command in a cmd prompt.

  
  

  Basically installing Dynamics CRM in the Default Website causes Exchange authentication to break. So i have learned the lesson the hard way to never do that and install Dynamics CRM in another virtual folder. I now need to work out how to edit that web.config file so that CRM works as well as everything else.

  
  

  If anyone knows how to do that please let me know.

  Also does anyone know what is the correct application pool, authentication & module setting for OWA ???

  
  

  Thanks.

  • Marked as answer by Gen Lin Tuesday, January 25, 2011 6:46 AM

  Monday, January 24, 2011 10:28 AM
• 

  

  0

  Sign in to vote

  Hi

  Thank you for sharing the resolution.

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

  Tuesday, January 25, 2011 6:47 AM
• 

  

  0

  Sign in to vote

  Hi Rashid,

  I have the same error with different system configuration. I have created the VM with Exchange Server 2010, CRM 2011 Server and SharePoint 2010 Server.
  I checked that my exchange server was working fine when my VM didn't had CRM installed in it.
  Now after reading your post I can understand that this issue can with my CRM installation.
  Also I have installed both CRM and SharePoint on different port (9876 and 1234 resp.)
  So now I understand that you want me to rename port 9876 ie CRM web.config file. 
  Could you please tell me rename it to what.
  Also I have a doubt, if I rename the web.config file of CRM 2011 wont it effect the proper functioning of the CRM.
  
  Thanks and Regards,
  

  Shivam Dixit 

  Tuesday, August 2, 2011 8:26 AM
• 

  

  0

  Sign in to vote

  Hi All, 
  
  This is the actual message I got.
   

  Error:
  

  
  Initialization failed.
  
  The following error occurred while attempting to connect to the specified exchange server.
  'win-n7miuk0ootj.contoso.com' :
  
  The attempt to connect to http://win-n7miuk0ootj.contoso.com/PowerShell using "Kerberos" authentication failed: Connecting to the remote server failed with the following error message: The WinRM client can not process the request. The authentication system requested by the client is not suported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted setting in the service configuration or specify one of the authentication mechanism supported by the server. To use Kerberos specify the computer name as remote destination. Also verify cleint destination and the remote computer are joined to a domain. To use the basic, specify the computer name as the remote destination, specify the Basic authentication and provide username and passwaord. Possible authentication mechanism reported by the server: For more information see the about_Remote_Troubleshooting Help Topics.

   

  Thanks and Regards,

  Shivam Dixit 

  • Proposed as answer by Mark B Rez Tuesday, October 23, 2012 6:50 PM

  Wednesday, August 3, 2011 1:57 PM
• 

  

  0

  Sign in to vote

  I was able to fix this error by changing the authentication type on the Powershell Site in IIS on the Mailbox server that was having the issue.  by default it was ASP.net and Windows Authentication.  i changed to Anonymous and Basic.  reset IIS , and it comes up fine now.

  Tuesday, October 23, 2012 6:53 PM
• 

  

  0

  Sign in to vote

  This fixed my issue.  I was working on it for days.  Thanks
  

  ---

  Randy Cheek

  Monday, July 22, 2013 4:01 PM