Applications Systems

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

This article resolves the following AppInsing for IIS error: Unable to create wsMan listener (Error code: 16024)

First published date

10/16/2018 1:27 PM

Last published date

6/25/2020 9:53 PM

Overview

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

Unable to create wsMan listener (Error code: 16024)

Product section

Server Application Monitor

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:

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)

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

Error Code 16024
http://stackoverflow.com/questions/5...2003-r2-server (© 2018 Stack Exchange Inc, available at https://stackoverflow.com/ , obtained on October 16, 2018)

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.