Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Issues following upgrade on additional poller - SWIS issues and Core BL not starting - Plugin "Core Business Layer" failed to start - Unknown provider Orion

Issues following upgrade on additional poller - SWIS issues and Core BL not starting - Plugin "Core Business Layer" failed to start - Unknown provider Orion

Updated May 2nd, 2016


The following issues are encountered on NPM 11.5.3 following an upgrade on the additional poller:

  • SWIS issues and Core BL not starting - Plugin "Core Business Layer" failed to start -- Unknown provider Orion.
  • Primary poller is up but the additional poller is showing as down in the polling engines window.

When editing an existing node that is connected through a remote poller and selecting the option to test the logon credentials, the following error message appears.
There is no endpoint listening on port 17777 and shows and undefined 500 Inner Exception


  • NPM 11.5.3

  • SAM 6.2.3 + Hotfix 1

  • SRM 6.2.1

  • NCM 7.4.1 +HF2

  • Recently upgraded primary/ additonal pollers to

    • NPM 11.5.3, SAM 6.2.3 + Hotfix 1, SRM 6.2.1 and NCM 7.4.1 +HF

  • Did the upgrade of the remote poller using the following:

    • and also


  • SWIS schemas were corrupted.
  • SWIS was working on the main poller but not on additional poller (APE).
  • Used hidden SWIS.ASPX page on Web Console to determine this:

  • The unknown Orion provider points to some problems with loading Orion data provider.

    There should be file called: C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\SolarWinds.Data.Providers.Orion.dll

  • Other errors found:
    • SolarWinds.Orion.Core.BusinessLayer and BusinessLayerHost.log
      2016-04-15 12:01:34,815 [7] ERROR SolarWinds.Orion.Common.SWEventLogging - Unhandled Exception caught in Core Service Engine startup. RunQuery failed, check fault information.

      2016-04-15 12:01:34,862 [7] FATAL SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerPlugin - Unhandled Exception caught in plugin startup.

      System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: RunQuery failed, check fault information. (Fault Detail is equal to InfoServiceFaultContract [ SolarWinds.Data.Query.QueryExecutionException: Unknown provider Orion.

    • SWIS is crashing every few minutes
      In 3 minutes had \LogFiles\InformationServiceV3\Orion.InformationService.log (3109 hits)

      2016-04-15 12:11:49,896 [44] ERROR SolarWinds.InformationService.Core.InformationService - SolarWinds.Orion.Core.Dependencies.InformationService.SwisHelper.Query() Exception caught in method RunQuery. System.NullReferenceException: Object reference not set to an instance of an object.

    • .NET Runtime

    • Faulting application name: SolarWinds.InformationService.ServiceV3.exe, version: 2015.1.3.7028, time stamp: 0x56719697 Faulting module name: KERNELBASE.dll, version: 6.1.7600.17206, time stamp: 0x50e669a2

    • Application Error
      Application: SolarWinds.InformationService.ServiceV3.exe

      Framework Version: v4.0.30319

      Description: The process was terminated due to an unhandled exception.

      Exception Info: System.MissingMethodException


  1. Back up and remove the additional poller's SWIS folder.
    C:\Program Files (x86)\SolarWinds\Orion\Information Service
  2. Copy the main poller's SWIS folder.
    C:\Program Files (x86)\SolarWinds\Orion\Information Service

Alternatively, you can also try to repair the Core on the additional poller.


Last modified
13:46, 17 Oct 2017