Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Essentials edition. Server & Application Monitor (SAM) is also available in a standalone module.

Other errors

This section provides details for troubleshooting AppInsight for IIS.

PowerShell 2.0 not installed

Issue: PowerShell 2.0 or later is not Installed.

Resolution: PowerShell is included in most version of Windows Server. Install PowerShell 5.1, if necessary

To configure permissions for PowerShell on the target server:

  1. On the remote computer, open the PowerShell console.
  2. Execute the following PowerShell command: Set-PSSessionConfiguration Microsoft.PowerShell -ShowSecurityDescriptorUI -force .
  3. When the permissions dialog box appears, enable Full Control.
  4. Ensure that the group to which the polling user belongs has access to Microsoft PowerShell.
  5. When finished, rerun the steps in Assign AppInsight for IIS to nodes in SAM.

Polling IIS unsuccessful

Issue: Polling IIS servers is unsuccessful.

Possible Errors: OutOfMemoryException, Not enough storage, WinRM, WinRM not functioning properly, and so on.

Cause: IIS servers hosting many sites may cause polling to be unsuccessful.

Resolution: Increase the polling frequency and Memory per Shell Limit on the target node as needed. When complete, rerun the steps in Assign AppInsight for IIS to nodes in SAM.

Complete the following to increase the polling frequency:

The default value is set at 300 seconds (five minutes). If you see more than a five-minute gap in a graphed widget, this value can be increased, as in any other SAM application.

  1. Click My Dashboards > Applications > SAM Summary, and then select an application to be taken to the Application Details view.
  2. Click Edit Application Monitor > Override template (next to Polling Frequency).
  3. Change to the desired value, and then click Submit.

Increase the memory per shell limit

  1. Run PowerShell via Run as Administrator and execute the following command to get the actual value:

    winrm get winrm/config/Winrs

  2. Examine MaxMemoryPerShellMB. If the value is less than 512, increase this value by executing the following command:

    Set-Item WsMan:\localhost\Shell\MaxMemoryPerShellMB NewValue -WarningAction SilentlyContinue;
    where the NewValue is the desired memory limit. If the error persists, increase the value again.