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'.
Issue:-
Not able to connect Exchange Management Console
and Exchange Management Shell
Error Message: -
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'.
For
more information, see the about_Remote_Troubleshooting Help topic.
+
CategoryInfo : OpenError:
(System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+
FullyQualifiedErrorId : PSSessionOpenFailed
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.
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'.
The
WinRM client received an HTTP status code of 403 from the remote WS-Management service.
Problem Statement: -
When you trying to access the Exchange Management
Console and Exchange Management Shell to do our administrative work, we could
not connect to it.
The above error will get generate in multiple
scenario’s.
Resolution: -
All of these error messages related with
PowerShell virtual directory and WinRM Feature.
1. Check
the Time sync between Exchange Server and your domain controller.
·
This is the common issue we will face
for the above issues.
W32tm /monitor
If you see any delay response between Exchange
server and Domain Controller.
Run w32tm /resync
2. If
you running Exchange servers in Hyper-V Environment, Follow the below navigation,
3. Configure Kerberos
Authentication
Start Internet Information Services
(IIS) Manager.
In the Connections pane, expand Default
Web Site, and then click PowerShell.
In the /PowerShell Home pane,
double-click Modules.
Confirm that Kerbauth is a
native module.
Confirm that the path of the
Kerbauth.dll file is C:\Program Files\Microsoft\Exchange
Server\v14\Bin\kerbauth.dll.
Verify that the Kerbauth module is
registered but not enabled on the default Web site. To do this, follow these
steps:
a.
Click
the default Web site in the Connections pane, and then double-click Modules
in the results pane.
b. In the Actions
pane, click Configure Native Modules.
c.
If
Kerbauth is not listed in the Configure Native Modules dialog
box, click Register. In the Register Native Module dialog box,
type the name and path of the Kerbauth module, and then click OK.
d. If Kerbauth is
enabled, click to clear the Kerbauth check box.
e.
Click
OK.
4.
Clear the SSL
Require settings in IIS.
·
Start
Internet Information Services (IIS) Manager.
·
In
the Connections pane, expand Default Web Site, and then click PowerShell.
·
In
the Results pane, double-click SSL Settings.
·
On
the SSL Settings property page, click to clear the Require SSL
check box.
·
In
the Actions pane, click Apply
5.
Install WinRM IIS
Extension:
Server Manager | Features | Add Features
| Win RM IIS Extension.
Thanks for visiting.
I had searched for hours on this issue with one of our clients, and finally option #4 worked for me after an IISReset! Thank you so much for this article!
ReplyDelete