Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
The following compiled errors provide additional information and troubleshooting AppInsight for IIS.
Issue: PowerShell 2.0 is not Installed
Resolution: Install PowerShell. See the following instructions for installing PowerShell andset the permissions.
To install PowerShell 2.0 on Server 2008, download the installation file for PowerShell 2.0 at http://support.microsoft.com/kb/968929/en-us and install it on the server.
PowerShell 2.0 is automatically installed on Server 2008 R2 and therefore no additional installation is required.
Set the appropriate permissions for PowerShell on the target server:
Set-PSSessionConfiguration Microsoft.PowerShell -ShowSecurityDescriptorUI -force. The permissions dialog should appear.
Issue: PowerShell WebAdministration snapin is not installed.
Information: For legacy systems with IIS 7.0 (Windows Vista, Windows 2008) PowerShell WebAdministration snapins are not part of IIS.
Resolution: Download and install the PowerShell WebAdministration snapins found at the following link: http://www.iis.net/downloads/microsoft/powershell
When complete, rerun the AppInsight for IIS Automatic Configuration Wizard.
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 AppInsight for IIS Automatic Configuration Wizard.
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 resource, this value can be increased, as in any other SAM application.
Increase the memory per shell limit
winrm get winrm/config/Winrs
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;
NewValueis the desired memory limit. If the error persists, the value should be increased again.