Troubleshoot AppInsight for IIS in SAM

Use the following sections to resolve AppInsight for IIS issues related to configuration and performance counters:

• Access is denied when configuring AppInsight for IIS
• Change between 32-bit and 64-bit polling
• Credentials test failed
• Polling fails due to a missing certificate
• IIS Polling Failed
• Node unreachable
• IIS version failed
• WinRM testing failed
• Error code 1367 incorrect credentials
• Error code 1726 server configuration
• AppInsight for IIS: Error code 16005 configuration exe not found
• AppInsight for IIS: Error code 16006 access denied
• Error code 16007 configuration exe has an invalid signature
• AppInsight for IIS: Error code 16008 network path not found
• Error code 16009 configuration file not found
• Error code 16013 unable to access remote admin share
• Error code 16022 HTTPS listener exists on port 5986
• Error code 16023 unable to create self-signed certificate
• Error code 16024 unable to create wsMan listener
• Error code 16029 failed to start Windows Remote Management
• Error Code 16049 unknown error IIS server configuration
• Error code 16090 PowerShell 2.0 or higher required
• Other errors
• Event IDs

In addition to the following troubleshooting tips, search the SolarWinds Success Center.

AppInsight for IIS widgets do not populate with data, or "No data is currently available" messages appears

Check the related application monitor, as well as the parent AppInsight for IIS template, to determine if any components were disabled.

InvokeMethod messages in logs

Starting in SAM 2020.2, WinRM is the default transport method to collect data for WMI-based component monitors. If monitoring Windows Server 2008 nodes with AppInsight for IIS, the following message may appear in application logs:

{{ERROR SolarWinds.APM.Probes.Management.WinRmFeatureService - Windows version 6.1.7601 with SP 1 does not support InvokeMethod }}.

The default log location is C:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs.

This message appears because the WinRM Invoke method is not supported by Windows Server 2008. Fallback should occur so polling continues for IIS servers.

Polling fails on Windows Server 2008 R2 SP1 nodes and applications switch to Unknown state

Windows Server .NET 4.8 agents expect a later version of PowerShell, so SolarWinds.APM.Probes.CustomWmiProbe- and Microsoft.Management.Infrastructure-related errors appear in logs. As a workaround, install PowerShell 3.0 or later on target servers. PowerShell 5.1 is recommended. Click here for details.