Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.6 Administrator Guide > Troubleshooting SAM > Error Code 16022 HTTPS listener exists on port 5986 issue in SAM

Error Code 16022 HTTPS listener exists on port 5986 issue in SAM

Table of contents
No headers

Updated: 3-9-2017

Error: An HTTPS listener currently exists on port 5986.

Cause: This error means that an HTTPS listener already exists on port 5986 and cannot be reused because it is not configured to listen for the target IIS server IP address.

Resolution: For details, see the log on the target computer located at: [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteIISConfigurator.log and RemoteIISConfiguratorPowerShell.log. For configuring WinRM using a different port, complete the following steps. When complete, rerun the AppInsight for IIS Automatic Configuration Wizard.

Configure WinRM??on a server:

Important: To configure the listener, change 5986 to an available port number throughout these steps.

  1. Open a command prompt with the option Run as Administrator.
  2. Type: winrm create winrm/config/listener?Address=*+Transport=HTTPS @{Port="5986";CertificateThumbprint="<Thumbprint value of certificate>";Hostname="<IP Address of Server>_Solarwinds_IIS_Zero_Configuration"} and press Enter.

  1. Verify the configuration by typing the following: winrm get winrm/config/listener?Address=*+Transport=HTTPS.


Next, create a firewall rule:

  1. Open PowerShell in the Run as Administrator context.
  2. Create a function for adding firewall rules using the following code:
    function Add-FirewallRule {
    $appName = $null,
    $serviceName = $null
    $fw = New-Object -ComObject hnetcfg.fwpolicy2
    $rule = New-Object -ComObject HNetCfg.FWRule
    $rule.Name = $name
    if ($appName -ne $null) { $rule.ApplicationName = $appName }
    if ($serviceName -ne $null) { $rule.serviceName = $serviceName }
    $rule.Protocol = 6 #NET_FW_IP_PROTOCOL_TCP
    $rule.LocalPorts = $tcpPorts
    $rule.Enabled = $true
    $rule.Grouping = "@firewallapi.dll,-23255"
    $rule.Profiles = 7 # all
    $rule.Action = 1 # NET_FW_ACTION_ALLOW
    $rule.EdgeTraversal = $false
  3. Run the function to create the firewall exception for WSMAN using the following command:

    Add-FirewallRule "Windows Remote Management" "5986" $null $null


  4. Verify the rule was created by navigating to Control Panel > Windows Firewall > Advanced Settings.
Last modified