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 Documentation > SAM 6.6.1 Administrator Guide > Troubleshooting SAM > Error Code 16024 unable to create wsMan listener issue in SAM

Error Code 16024 unable to create wsMan listener issue in SAM

Table of contents
No headers

Updated: 3-9-2017

Error: Unable to create wsMan listener.

Cause: This error means that an unexpected error occurred during wsMan listener creation.

Resolution: Check the configuration script log file located on the target IIS server at, [ALLUSERSPROFILE]\ProgramData\Solarwinds\Logs\APM\RemoteIISConfigurator.log. When complete, rerun the AppInsight for IIS Automatic Configuration Wizard.


See also this article.

Last modified