Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

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)

Overview

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

Unable to create wsMan listener (Error code: 16024)

Environment

All SAM versions

Resolution

Ensure the correct SPNs (Service Principal Names) are added.
Note: Microsoft Windows Server Support Packs may have the correct SPNs upon installation.
Important:
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.cz Server1

 

See the following for more information:

 

Last modified

Tags

Classifications

Public