Another WinRM "client cannot process the request" Issue - EMC Won't Connect

  • Thread starter jpalarchio
  • Start date Views 3,038
Status
Not open for further replies.
J

jpalarchio

Exchange 2010, Update Rollup 4 (UR4 may have been where my issue started)

When launching the EMC, I receive the following message:

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.

I've gone through every article I could find on this topic and none of them have worked.

I suspect the problem started as a result of one of three things:
Installation of Update Rollup 4 An attempt to setup http redirect so http://server/ would forward to https://server/owa (this has since been removed) A change of the IIS bindings to only use the primary NIC (this has since been removed)

The common trick seems to be to uninstall and reinstall the " WinRM IIS Extension" however that did not work. I have also confirmed the proper configuration of the kerbauth and WSMan modules within IIS.

I've tried both uninstalling UR4 and reinstalling it multiple times (as has worked for some) and the same issue occurs.

Any assistance would be appreciated.
 
J

jpalarchio

Ended up contacting PSS on this and they were able to quickly resolve.

The issue was a result of a web.config file residing in " C:\inetpub\wwwroot" . We renamed the file and the console and shell worked fine.

From the contents of the file, it looks like it was created sometime when http redirection was being setup.
 
Status
Not open for further replies.
Top