Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Node down alerts not triggered (Collector SDF is Corrupt) - Plugin Collector Business Layer Plugin failed to start

Node down alerts not triggered (Collector SDF is Corrupt) - Plugin Collector Business Layer Plugin failed to start

Created by Kevin Twomey, last modified by Rodim Suarez on Mar 10, 2017

Views: 12 Votes: 1 Revisions: 4


Alert rule does not triggered on node and the following scenarios are observed:

  • NodeXYZ ( - Node Status - Node is Down
  • All Alerts this Object can trigger (1) – «Node is down»
  • «Node is down» triggered condition: [Node Status is equal to Down]
    [Node IP_Address does not start with 192.168.] [Node Display Name does not contain -router]
  • Evaluate the trigger condition every 1 minute


  • NPM 11.5.3 

  • NTA 4.1.0

  • VNQM 4.2.3 

  • NCM 7.3.2



BL Issues and Collector SDF is corrupt.

SolarwindsDiagnostics\LogFiles\Orion\BusinessLayerHost.log (3 hits)
SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Starting plugin: "Collector Business Layer Plugin"
SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "Collector Business Layer Plugin" failed to start.

System.TypeInitializationException: The type initializer for 'SolarWinds.Collector.SqlCeHelper' threw an exception.
---> System.AccessViolationException: Attempted to read or write protected memory.
This is often an indication that other memory is corrupt. 
at System.Data.SqlServerCe.WinTrust.VerifyEmbeddedSignature(String filePath)


Replace the Collector Files

  1. Stop all Orion services from Orion Service Manager.
  2. Go to C:\ProgramData\Solarwinds\Collector\Data\JobsTracker.sdf and Polling Controllor.sdf file
    • Rename hem to *******OLD.sdf 
  3. Then create a copy of C:\ProgramData\Solarwinds\Collector\Data\***** Blank.sdf.
    • Rename it to JobTracker.sdf and PollingControllor.sdf.
  4. This way you have the old one to revert back to and you always have a blank copy in case issue reoccurs. 
  5. Right click on properties of the .sdf you have created and deselect the read only box and click ok.

If still issues after restarting services, try this also.
Repair Collector

  1. Open C:\ProgramData\Solarwinds\Collector\Data\Installers
  2. Run the CollectorInstaller.msi and select Repair.




Last modified
19:57, 9 Mar 2017