Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for Exchange: WinRM testing failed

AppInsight for Exchange: WinRM testing failed

Created by Tiarnan Stacke, last modified by MindTouch on Jun 23, 2016

Views: 3,145 Votes: 1 Revisions: 4

Overview

Unable to connect to AppInsight for Exchange with the following error:

WinRM testing failed with the following error:
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: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
PowerShell Exchange web site test was successful.

Environment

  • SAM v6.1 and later

Cause 

The WinRM Service on the Exchange Mailbox is not listening on any IP addresses.

Resolution

Confirm the configuration on the Exchange Server

  1. RDP to the Exchange Server that you are attempting to register for monitoring.
  2. Open a PowerShell session.
  3. Run the following command winrm get winrm/config/listener?Address=*+Transport=HTTPS.
  4. Confirm that ListeningOn lists IP addresses that it is listening on. It SHOULD NOT have "null" like the image below:
    PowershellOutput.png

 

If you have the same as the above image, then this issue can be caused by an incorrect Group Policy Configuration.


Confirm the following in your Group Policy

  1. Open your Group Policy Editor.
  2. Go to Computer > Policies > Windows Components > Windows Remote Management (WinRM) > WinRM Service.
  3. Check the configuration of the "Allow automatic configuration of listeners" policy.
  4. Verify that the Policy configuration is correct.
    Note: There should not be quotes entered into the fields available. The configuration should look like the following:

 

If you need to change this policy, you will need to force a Group Policy Update on the Exchange server and try running the AppInsight Configuration from SAM again.

 

Last modified

Tags

Classifications

Public