Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > AppInsight for IIS error: Unable to create wsMan listener (Error code: 16024)

AppInsight for IIS error: Unable to create wsMan listener (Error code: 16024)


This article provides brief information and steps to resolve the following AppInsing for IIS error:

Unable to create wsMan listener (Error code: 16024)


All SAM versions


Ensure the correct SPNs (Service Principal Names) are added.
Note: Microsoft Windows Server Support Packs may have the correct SPNs upon installation.
If SPNs are already mapped for different user account, you should remove the SPNs before running WinRM.


Examine the SPNs using the List option:

1. From a PowerShell command line, enter the following:

setspn.exe -L server1

Here you can examine the list to see which SPNs are missing. (For example: HTTP)


2. If HTTP is missing, add the HTTP option for the target server by entering the following command:

setspn.exe -A HTTP/Server1 Server1 and setspn.exe -A HTTP/ Server1


See the following for more information:


Last modified