- Remove From My Forums
-
Question
-
Hi All,
I have installed the Exchange 2010 Management Tools and a few roles on our DC (Windows Server 2008 R2) but i cannot even connect to it to configure anything.
If i use the management tools GUI i get an error message saying:
«Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.»
Using the Exchange Management Shell is get a similar error:
«Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId: PSSessionOpenFailed»This comes up 3 times and then said it failed to connect and to enter the Server FQDN i want to connect to.I have seen other posts where they have said to disable anonymous access for PowerShell in IIS which i have done and to also run the set-user yourusername -remotepowershellenabled:$true which i cannot run because i cannot even connect into it via PowerShell.
Tried to see if there was a way to reinstall the management tools because i have a feeling they didnt install properly but cant find a way to do that.
Tried to uninstall everything but i cannot because it says there are already mailboxes created (presume some default ones) but i cannot connect to remove them to uninstall.
I seem to have reached a wall and cannot see how to proceed.
Please help. Thanks.
Answers
-
Hi All,
I ended up having to denote the server back to a member server then recover it from a very old backup and go through the whole process of promoting it to a DC again. Once i did all that and got it back to how it was prior to the exchange install i ran setup with the recoverserver switch (setup /m:RecoverServer) as all the AD changes where still in place and setup would not run normally.
Once the recover finished i had all the roles and management tools installed again and i was able to connect.
-
Marked as answer by
Tuesday, January 12, 2010 1:07 AM
-
Marked as answer by
- Home
- Microsoft
- Exchange 2010
- The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received An Http Server Error Status (500)
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 June 6, 2012. Posted in Exchange 2010
After upgrading a Server 2008 server recently that was running Exchange 2010 I came across this error.
The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received An Http Server Error Status (500)
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.
Tags: emc error 500
Allen White
Allen is an IT Consultant and holds the following accreditations. MCSA, MCSE, MCTS, MCITP, CCA, CCSP, VCP 4,5, 6 and HP ASE, AIS — Network Infrastructure.
Search
- Remove From My Forums
-
Question
-
Good morning,
I have major problems with exchange 2010 this morning.
First off, exchange stopped sending and receiving any emails- whether internal or external. We are running a server 2008 R2 domain and exchange 2010 is installed on a Server 2008 virtual machine.
I tried simply rebooting the server and then tried logging on and getting into the Exchange Management Console. I receive the following error in the exchange management console:Initialization failed
The following error occurred while attempting to connect to the specified Exchange server ‘exchangesvr.chs.internal’;
The attempt to connect to
http://exchangesvr.chs.internal/Powershell using «Kerberos» authentication failed: Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any
other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.I followed the steps listed here:
http://technet.microsoft.com/en-us/library/ff607221(EXCHG.80).aspx
but everything appeared to be correct. I did not have to make any changes because everything was set as it should be according to that information.Any help would be much appreciated.
Best regards
Katrina
Answers
-
After spending a whole day on this issue we’ve decided to build a new server and restore as much as we can from the old server. Not ideal, but all we can do I think.
-
Marked as answer by
Monday, September 19, 2011 1:44 AM
-
Marked as answer by
| title | description | author | audience | ms.topic | ms.author | manager | localization_priority | ms.custom | search.appverid | appliesto | ms.date | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Connecting to the remote server failed when start Management Shell or Console |
Connecting to the remote server failed with the following error message when you start the Exchange Management Shell or the Exchange Management Console. |
simonxjx |
ITPro |
troubleshooting |
v-six |
dcscontentpm |
Normal |
|
MET150 |
|
3/31/2022 |
«Connecting to the remote server failed with the following error message» error when you start the Exchange Management Shell or the Exchange Management Console
Symptoms
When you try to start the Microsoft Exchange Management Shell (EMS) or the Microsoft Exchange Management Console (EMC) on a server that is running Microsoft Exchange Server, you receive one of the following error messages:
-
Error message 1
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 information, see the about_Remote_Troubleshooting Help topic.
-
Error message 2
Connecting to remote server failed with the following error message: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.
-
Error message 3
Connecting to remote server failed with the following error message: The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.
-
Error message 4
Connecting to remote server failed with the following error message: The connection to the specified remote host was refused. Verify that the WS-Management service is running on the remote host and configured to listen for requests on the correct port and HTTP URL. For more information, see the about_Remote_Troubleshooting Help topic.
-
Error message 5
Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 403 from the remote WS-Management service.
-
Error message 6
Connecting to the remote server failed with the following error message: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
-
Error message 7
Connecting to remote server failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service:
-
Error message 8
Connecting to remote server failed with the following error message: The WS-Management service does not support the request.
-
Error message 9
Connecting to remote server failed with the following error message: The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer.
Resolution
To resolve these problems, run the «Exchange Management Troubleshooter» (EMTshooter).
About the EMT shooter
The EMTshooter runs on the local (target) Exchange server and tries to identify potential problems that affect the management tools that are connected to it.
The troubleshooter runs in two stages. First, it examines the IIS Default Web Site, the PowerShell vdir, and other critical areas to identify known causes of connection problems. If the tool identifies a problem that affects one of the pre-check processes, it makes a recommendation to resolve the problem. If the pre-checks pass, the troubleshooter tries to connect to the server exactly like the management tools would connect. If that connection attempt still causes a WinRM-style error, the troubleshooter tries compare that error to a list of stored strings that are collected from related support cases. If a match is found, the troubleshooter displays the known causes of that error in the CMD window.
The following screen shot shows how this display might appear.
:::image type=»content» source=»media/connecting-remote-server-failed/emt-shooter.png» alt-text=»Screenshot of how this display might appear.»:::
The EMTshooter logs events in the «Microsoft-Exchange-Troubleshooters/Operational» event log. All results that are displayed in the CMD window are also logged in the event log to create a record.
Things to remember
-
Depending on your current settings, you may have to adjust the execution policy on your computer to run the troubleshooter by using one of the following commands:
-
Set-ExecutionPolicy RemoteSigned
-
Set-ExecutionPolicy Unrestricted
[!IMPORTANT]
Remember to revert to the usual settings after you run the troubleshooter.
-
-
You must run this version of the troubleshooter on the server that is running Exchange Server that the management tools do not connect to.
-
In order to run the troubleshooter, you must have the user rights to log on locally to the Exchange server. This is a current requirement of the tool. Additionally, you must have the user rights to run Windows PowerShell.
How to install EMTshooter
To install the EMT shooter, follow these steps:
- Download the troubleshooter compressed file that has a .zip filename extension from here.
- Extract the four files that are included in the .zip file into a folder, and then rename the file extensions to .ps1.
- Run EMTshooter.ps1 from a standard (and local) Windows PowerShell window.
References
For more information about the problems that are processed by EMTshooter and the causes of some of those problems, see the following Exchange Team Blog articles:
Troubleshooting Exchange 2010 Management Tools startup issues
Resolving WinRM errors and Exchange 2010 Management tools startup failures
One quite common error I faced during the Exchange 2010 era is the WinRM HTTP Error:
If i use the management tools GUI i get an error message saying:
“Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.”
Using the Exchange Management Shell is get a similar error:
“Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorId: PSSessionOpenFailed”
FIRST THING YOU MUST DO: DO NOT PANIC !
DO NOT REBOOT THE SERVER !!!
I WILL EXPLAIN HOW TO SOLVE THIS IN A FEW EASY STEPS:
1. When you open the EMC ( Exchange Management Console ), you will get an error similar to this:
2. Go to START / Administrative Tools / Server Manager / Features / Add Features / And check WinRM IIS Extensions / NEXT / NEXT / CLOSE:
!!! IF YOU ALREADY HAVE THIS ROLE INSTALLED, JUST REINSTALL IT !
3. Close / Reopen EMC and it will work like a charm ( NO REBOOT REQUIRED ):
ENJOY.
And if you encounter any problems feel free to comment / contact me.