Submit a ticketCall us

AnnouncementsCome see SolarWinds at VMUG Frankfurt

SolarWinds is delighted to attend the upcoming VMUG which will take place at Kap Europa in Frankfurt on June 19th, 2018.

See event details.

Home > Success Center > Network Performance Monitor (NPM) > Forcing the Business Layer to load plugins in a separate or 64-bit process in NPM 12

Forcing the Business Layer to load plugins in a separate or 64-bit process in NPM 12

Updated October 26, 2017


This article provides information about changing the behavior of Business Layer (Module Engine) to load plugins as separate processes, as opposed to a single process (default). This is especially beneficial in large or complex environments.


Products running on Orion Platform version 2016.1 and later, such as:

  • NPM 12.0 and later
  • SAM 6.2.4 and later
  • NCM 7.5.0 and later
  • SRM 6.3 and later
  • UDT 3.2.4 and later
  • VNQM 4.2.4 and later


  1. Log in to the Orion Web Console.
  2. Access the Centralized Settings feature by adding the following to the URL:
    For example: http:/<server_name>:8787/Orion/Admin/AdvancedConfiguration/Global.aspx
  3. Select the Global tab to apply the setting to all servers, or select a specific server.
  4. Scroll down to the section SolarWinds.BusinessLayerHost.BusinessLayerHostSettings and locate the ForcePluginsInSeparateProcess setting.

    For installations running on Orion Platform 2016.1 - 2017.1:

    • Select the box to separate processes. 
    • Clear the box to use a single process.

    For installations running on Orion Platform 2017.3 and later, choose one of the following values:

    • True - Always use separate processes.

    • False - Always use a single process.

    • Auto (default) - If enough memory (8 GB) is installed and the Orion database is not on the same machine, separate process are used

  5. Click Save.
  6. Restart the Orion services.





Last modified