06 Jun 2012

The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received An Http Server Error Status (500)

Written by Allen White on. Posted in Exchange 2010

After upgrading a Server 2008 server recently that was running Exchange 2010 I came across this error.

There are a few variations of the message also namely this one below.

The attempt to connect to http://server.domainname.com/powershell using “kerberos” authentication failed:Connecting to remote server failed with the following message:The WinRm client cannot process the request.It cannot determine the content type pf the HTTP response from the destination computer. The content type is absent or invalid.

The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received And Http Server Error Status (500)

This is down to the WinRM client becoming corrupt. This is an easy fix to do via the exchange powershell console. do the following.

We first need to enable to server manager plug in. To do so run this command

Import-Module ServerManager

Then run this command te remove the service.

Remove-WindowsFeature WinRM-IIS-Ext

Then we need to reinstall WinRm. To do so run this command as seen below.

Add-WindowsFeature WinRM-IIS-Ext

Add-WindowsFeature WinRM-IIS-Ext

You will now find that you can launch the Exchange Management console without any issues, View to video below for a full step by step guide on fixing the “The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received And Http Server Error Status (500) ” issue.

Related Problems

Cannot Install .Net Framework 3.5.1 On Server 2008 – 0×80070643

When installing the .net framework 3.5.1 feature on server 2008 it fals with the error 0x80070643, this can be fixed with this solution

READ SOLUTION

Outlook 2003 Gives Connect To Instance Error When Connecting To Exchange 2010

When you connect to exchange 2010 with outlook 2003 , you may see the error connect to instance. This is a known issue and microsoft have provided a fix

READ SOLUTION

Exchange 2010 /2013 Queue 451 4.4.0 Primary target IP address responded with: “451 5.7.3 Cannot achieve Exchange Server authentication

While migrating from exchange 2003 to exchange 2010 you see mail queus building up between the exchange 2010 server send mail to exchange 2003. The error yuo see is Exchange ...

READ SOLUTION

Set OWA Authentication

Setup OWA authentication methods in exchange 2007/2010.In exchange 2010 and 2007, exchange gave you the option of multiple methods of loggin into owa here is how to setup these owa ...

READ SOLUTION

Process MSEXCHANGE AD TOPOLOGY SERVICE.EXE (PID=1756). Topology discovery failed, error 0x8007077f

Exchange store will not mount because it cannot see active directory, sites and services issue.error 0x8007077f seen in logs, here is how to fix.Process MSEXCHANGE AD TOPOLOGY SERVICE.EXE

READ SOLUTION

You cannot mount a new Exchange Server 2010 Mailbox database

If you have just installed exchange 2010, you may find that the default datastore will not mount this is a known issue , Here is how to fix the ...

READ SOLUTION

Client Printers Not Mapping In Xen App / Presentation Server

When attaching to to a citrix session a client printer will not connect automatically even thought you have set it up,here is the fix,Event ID: 1116, AddPrinter() Error 0x3EB

READ SOLUTION

Setup iPad Or iPhone to Connect to Microsoft Exchange 2007,2010 and 2013

A step by step guide on how to connect your apple iPhone or iPad to microsoft exchange server.How to configure mail to connect to exchange

READ SOLUTION

Cannot Install .Net Framework 3.5.1 On Server 2008

Outlook 2003 Gives Connect To Instance Error When

Exchange 2010 /2013 Queue 451 4.4.0 Primary target

Set OWA Authentication

Process MSEXCHANGE AD TOPOLOGY SERVICE.EXE (PID=1756). Topology discovery

You cannot mount a new Exchange Server 2010

Client Printers Not Mapping In Xen App /

Setup iPad Or iPhone to Connect to Microsoft

Tags: emc error 500

Trackback from your site.

Allen White

Allen is a Technical Consultant for an IT company in the North East of England and holds the following accreditations. MCSA, MCSE, MCTS, MCITP, CCA, CCSP, VCP 4,5 and HP AIS - Network Infrastructure. I run this site is my spare time so if I help you then PLEASE take the time to share using the share tools on the site.

Comments (4)

Horatio

October 13, 2012 at 6:49 pm | #

I ran those codes and I am still getting the same error message. I even get that error message in the exchange management shell. Any other tricks to fixing it?

Reply
JoshB

October 29, 2012 at 7:48 pm | #

I got this error after upgrading 2008R2 Std to Enterprise. Your fix resolved my issue. Thank you.

Reply
- Allen White
  
  October 29, 2012 at 8:07 pm | #
  
  Glad to help josh…just a note, MS do NOT support exchange 2010 when it is on a server that has been upgraded from 2008 standard to to 2008 enterprise .So if you ever log a support call to MS then it my be wise to “forget” thats happend
  
  Reply
Leneesh Thoppil Ravi

January 14, 2013 at 9:12 am | #

Hi
I follow your steps I am getting after the command, please see below Error

New-PSSession : Cannot bind parameter ‘ConnectionUri’. Cannot convert value “http:///powershell?serializationLevel=Full
;ExchClientVer=14.1.218.15″ to type “System.Uri”. Error: “Invalid URI: The hostname could not be parsed.”
At line:1 char:29
+ New-PSSession -ConnectionURI <<<< "$connectionUri" -ConfigurationName Microsoft.Exchange -SessionOption $so
+ CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand

Reply