Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.5 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.

    File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/1D0/dosa_604x83.png
  1. Verify the configuration by typing the following: winrm get winrm/config/listener?Address=*+Transport=HTTPS.

    File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/1D0/dosb.png

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 {
    param(
    $name,
    $tcpPorts,
    $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
    $fw.Rules.Add($rule)
    }
  3. Run the function to create the firewall exception for WSMAN using the following command:

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

    File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/1D0/fwrule.png

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

Tags

Classifications

Public