Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Unable to poll after upgrading to NPM 12.0.1 or SAM 6.3

Unable to poll after upgrading to NPM 12.0.1 or SAM 6.3

Updated March 13, 2017

Overview

After upgrading to NPM 12.0.1 or SAM 6.3 (Orion Core 2016.1), you notice that there is no polling occurring. All services appear to be started but there is no polling and the Menu Bars are not populating correctly.

You may also see an error in the logs similar to the following:

2016-10-12 13:21:26,611 [7] ERROR SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "Core Business Layer" failed to start.
System.IO.FileNotFoundException: Could not load file or assembly 'SolarWinds.NCM.Contracts, Version=7.4.0.1368, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'SolarWinds.NCM.Contracts, Version=7.4.0.1368, Culture=neutral, PublicKeyToken=null'

Environment

  • SAM 6.3
  • NPM 12.0.1
  • Core 2016.1

Cause 

There are old .dll files from previously installed modules that causing the Core Business Layer to crash.

Resolution

  1. Check the error message to see which module is causing the crash. In the example above, it is NCM:
    2016-10-12 13:21:26,611 [7] ERROR SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "Core Business Layer" failed to start.
    System.IO.FileNotFoundException: Could not load file or assembly 'SolarWinds.NCM.Contracts, Version=7.4.0.1368,
  2. Copy and paste the folder to your desktop as a backup
  3. Remove the NCM folder from the SolarWinds Orion installation folder which is usually be default:
    C:\Programfiles(x86)\Solarwinds\Orion\NCM
  4. Restart all Orion Services.
  5. Try navigate to the Web Console.

 

Last modified
23:47, 12 Mar 2017

Tags

Classifications

Public