Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
Updated July 20, 2016
This article addresses the issue where an additional poller cannot be added to a node unless it is added through the primary poller, edited and assigned to the additional poller.
The following error also appears in the CoreBusinessLayer.log file:
2016-07-18 08:34:44,467  ERROR SolarWinds.Orion.Core.BusinessLayer.BackgroundInventory.PluginsFactory - Failed to initialized assembly E:\Program Files (x86)\SolarWinds\Orion\HardwareHealth\SolarWinds.HardwareHealth.Collector.dll
System.BadImageFormatException: Could not load file or assembly 'file:///E:\Program Files (x86)\SolarWinds\Orion\HardwareHealth\SolarWinds.HardwareHealth.Collector.dll' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'file:///E:\Program Files (x86)\SolarWinds\Orion\HardwareHealth\SolarWinds.HardwareHealth.Collector.dll'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
at System.Reflection.Assembly.ReflectionOnlyLoadFrom(String assemblyFile)
at SolarWinds.Orion.Core.BusinessLayer.BackgroundInventory.PluginsFactory.ProcessAssembly(String fileName)
at SolarWinds.Orion.Core.BusinessLayer.BackgroundInventory.PluginsFactory.Process(IEnumerable`1 files)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
NPM 10.5 and later
This occurs when certain .dlls on the additional poller are either corrupted or blocked by the server. In this case, the problematic dlls are the Hardware Health dlls.
Note: The reason why you must extract the zip, then re-zip it and extract it again is because Windows Server 2008 and later automatically block any dll file extensions that did not originate from it. By extracting the zipped directory, all of those dlls from the primary will be blocked. The easiest way to get around this is to then zip all of those extracted files into a new zip file created on that server. This will cause the server to automatically trust all of the dlls in the zip as the dlls originated on the server. Once you extract them back out to a new directory, all of those dlls will be trusted.