"Connecting to the remote server failed with the following error bulletin" mistake when y'all start the Exchange Direction Beat or the Exchange Direction Console

  • Article
  • 4 minutes to read
  • Applies to:
    Exchange Server 2010 Service Pack iii, Commutation Server 2010 Enterprise, Substitution Server 2010 Standard

Symptoms

When you try to starting time the Microsoft Exchange Direction Beat out (European monetary system) or the Microsoft Exchange Management Panel (EMC) on a server that is running Microsoft Exchange Server, you lot receive i of the post-obit error messages:

  • Error bulletin 1

    Connecting to remote server failed with the following error message: The WinRM client cannot procedure the request. It cannot decide the content type of the HTTP response from the destination computer. The content blazon is absent or invalid. For more data, see the about_Remote_Troubleshooting Aid topic.

  • Error message ii

    Connecting to remote server failed with the post-obit error bulletin: The WinRM client sent a request to an HTTP server and got a response proverb the requested HTTP URL was not available. This is usually returned past a HTTP server that does not support the WS-Management protocol. For more information, run across the about_Remote_Troubleshooting Assistance topic.

  • Fault 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 data almost the cause of the failure. For more information, run into the about_Remote_Troubleshooting Help topic. It was running the command 'Find-ExchangeServer -UseWIA $truthful -SuppressError $true'.

  • Mistake message iv

    Connecting to remote server failed with the following error bulletin: 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 than information, run across the about_Remote_Troubleshooting Help topic.

  • Error message 5

    Connecting to remote server failed with the following mistake message: The WinRM client received an HTTP condition code of 403 from the remote WS-Management service.

  • Error bulletin 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 bachelor. This is usually returned by a HTTP server that does not back up the WS-Management protocol.

  • Error message 7

    Connecting to remote server failed with the following error message: The customer 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-Direction service running on the destination, most unremarkably IIS or WinRM. If the destination is the WinRM service, run the following control on the destination to analyze and configure the WinRM service:

  • Fault bulletin 8

    Connecting to remote server failed with the following fault message: The WS-Direction service does not support the asking.

  • Mistake bulletin 9

    Connecting to remote server failed with the following error bulletin: The WinRM client cannot procedure the request. The WinRM client tried to use Kerberos authentication mechanism, only the destination computer.

Resolution

To resolve these bug, run the "Exchange Direction Troubleshooter" (EMTshooter).

About the EMT shooter

The EMTshooter runs on the local (target) Commutation server and tries to identify potential problems that touch the management tools that are connected to it.

The troubleshooter runs in two stages. Kickoff, it examines the IIS Default Web Site, the PowerShell vdir, and other critical areas to place 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 similar the management tools would connect. If that connection try still causes a WinRM-style fault, 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 post-obit screen shot shows how this display might announced.

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 electric current settings, yous may have to accommodate the execution policy on your figurer to run the troubleshooter past using i of the following commands:

    • Set up-ExecutionPolicy RemoteSigned

    • Ready-ExecutionPolicy Unrestricted

      Of import

      Remember to revert to the usual settings afterwards y'all run the troubleshooter.

  • You lot must run this version of the troubleshooter on the server that is running Exchange Server that the direction tools do not connect to.

  • In lodge 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, y'all must have the user rights to run Windows PowerShell.

How to install EMTshooter

To install the EMT shooter, follow these steps:

  1. Download the troubleshooter compressed file that has a .zip filename extension from here.
  2. Extract the four files that are included in the .zip file into a folder, then rename the file extensions to .ps1.
  3. Run EMTshooter.ps1 from a standard (and local) Windows PowerShell window.

References

For more information well-nigh the bug that are processed by EMTshooter and the causes of some of those bug, encounter the following Substitution Squad Blog manufactures:

Troubleshooting Exchange 2010 Management Tools startup issues

Resolving WinRM errors and Exchange 2010 Management tools startup failures