Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Server & Application Monitor (SAM) > AppInsight for Exchange error: Remote configuration failed

AppInsight for Exchange error: Remote configuration failed

Overview

The following error message appears when trying to configure AppInsight for Exchange:
Remote Configuration Failed
Remote configuration was unsuccessful due to the following: "WinRM test was successful.
PowerShell Exchange web site testing failed with the following error: Connecting to remote server
failed with the following error message : The WinRM client received an HTTP bad request status
(400), 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."


392275_1.png

 

As a result of this error, when you edit the Site Bindings, the HTTPs binding is set to all unassigned address on port 443 with a valid SSL certificate as shown below.


392275_2.png

Environment

SAM version 6.2

Cause

This issue is caused by a missing PowerShell https endpoint.

Resolution

Note: The error on the component will still appear upon application of the resolution as the Server Mailboxes are polled once every day. The error should no longer appear the following day or during the next polling.


1. Create a wsMan listener by initializing $targetIP variable with the Exchange Server IP.
    Run the next query on the Exchange Server and give the output:
    $targetIP = "192.168.3.52";
  $hostname = $targetIP + "_Solarwinds_Exchange_Zero_Configuration";
  $lifeTimeDays = 365 * 50; 
  try{
  # Get the thumbprints of the SSL certificates that match the hostname
  Write-Output "SSL certificates info:";
  Get-Childitem -path cert:\LocalMachine\My | Where-Object {$_.Subject -eq "CN=$hostname"};
  $thumbprints = Get-Childitem -path cert:\LocalMachine\My | Where-Object {$_.Subject -eq "CN=$hostname"} | Select-Object -Property Thumbprint; 
  # PowerShell magic to retrieve the first matching thumbprint (there'll probably only be one anyway) 
  $thumbprint = @($thumbprints)[0].Thumbprint;
  Write-Output "Retrieved thumbprint:";
  Write-Output $thumbprint; 
  # Create a WinRM listener, identifying the SSL certificate by the thumbprint
  New-WSManInstance WinRM/Config/Listener -SelectorSet @{Address = "*"; Transport = "HTTPS"} -ValueSet @{Hostname = $hostname; CertificateThumbprint = $thumbprint}; 
  } catch {
  Write-Output "Unable to create wsMan listener. ERROR: $($Error[0])";
  }
2. Recycle the following application tools:

  •     MSExchangePowerShellFrontEndAppPool (Default Web Site\PowerShell app.pool)
  •     MSExchangePowerShellAppPool (Exchange Back End\PowerShell app.pool)
  •     MSExchangeOWAAppPool (Default Web Site app.pool)
  •     DefaultAppPool (Exchange Back End app.pool)

    Refer to the Recycle an Application Pool on Demand (IIS 7) for more information regarding recycling application pools.

 

To test the Orion server's connection to the powershell website:

1) Rdp to the polling engine assigned to poll the node on that application

2) Open IE -> try to hit https://${IP}/powershell/

3) This website needs to resolve without error on the polling engine polling the exchange server for the Application to work.

4) This error is caused by the solarwinds server not being able to hit the powershell website. This can be caused by the exchange powershell website's certificate being invalid or expired, incorrect port binding on the website, or firewall issues.

 

 

Last modified
14:56, 31 Aug 2017

Tags

Classifications

Public