Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Web Console errors and w3wp.exe uses high memory

Web Console errors and w3wp.exe uses high memory

Updated November 1st, 2016


This article describes an issue where the Orion Web Console displays an error, preventing access to further pages until the SolarWinds Orion Application Pool is restarted. When this issue occurs, w3wp.exe or SWIS V3 may consume excessive memory and the C:\ProgramData\Solarwinds\Logs\Orion\OrionWeb.log will have multiple entries for the following:


WARN  SolarWinds.InformationService.Contract2.InfoServiceProxy - Support! -- LONG RUNNING QUERY: 162113.3738 ms:
    p.EntityName as EntityName,
    p.Name as Name,
    p.DisplayName as DisplayName,
    p.Type as Type,
    p.FilterBy as FilterBy,
    p.GroupBy as GroupBy,
    p.Values as Values,
    p.IsKey as IsKey,
    p.IsInherited as IsInherited,
    p.MinValue as MinValue,
    p.MaxValue as MaxValue,
    p.Events as Events,
    p.IsNavigable as IsNavigable,
false as IsFavorite
FROM Metadata.Property as p
ORDER BY p.EntityName, p.Name RETURN XML RAW



  • NPM 12.0
  • NPM 12.0.1


Issue 1: A bug with the algorithm that renders the maps has a code for resolving the macros (there are some supported in the maps) and the macros need a query to the SWIS entities structure.

Issue 2: Packages/schema files are damaged or corrupt.


Solution 1

Enable schema caching. 

  1. Find the file C:\inetpub\SolarWinds\web.config 
  2. Add the following key inside the web.config <appSettings> sections:
    <add key="SwisEntityMacroParserPluginCacheEnabled" value="True" />
    Adding this key above enables schema caching, which is used for the alerting service.
  3. Add the following key to SolarWinds.InformationService.ServiceV3.exe.config inside the <runtime> section. The file can be found in the default location C:\Program Files (x86)\Common Files\Solarwinds\Information Service\V3\
    <gcServer enabled="true" />
    Adding this key enables trash collection within the process.
  4. Restart IIS (IISRESET) and the SolarWindsInformationServicev3 for the changes to take effect.

Solution 2
Perform a package repair.

  1. Locate the ConfigurationWizard.exe.config file . By default, this is in C:\Program Files (x86)\SolarWinds\Orion
  2. Back up the file and then open in Notepad.
  3. Locate the XML element <appSettings>
  4. Add the line <add key="Packaging.Internal.RepairMode" value="true"/> element into <appSettings> and save the file.
  5. Stop all SolarWinds services and the website.
  6. Run the SolarWinds Configuration Wizard and choose all three options.
  7. Set the key in the ConfigurationWizard.exe.config file to False after the Configuration Wizard has completed.

Solution 3:
This is fixed in Core 2017 NPM 12.1 and also we check and repair packages during a configuration wizard run by default.



Last modified