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) > Core Business Layer failed to start and polling engine is down

Core Business Layer failed to start and polling engine is down

Created by Carlos Vigier, last modified by Norbert Skurzewski on Apr 25, 2017

Views: 422 Votes: 10 Revisions: 25

Overview

Data is unavailable in List Resources and the polling engine status is Down.

The following error message can be found in the module engine log (C:\ProgramData\Solarwinds\Logs\Orion\BusinessLayerHost.log):

ERROR SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "Core Business Layer" failed to start.
System.InvalidCastException: Specified cast is not valid.
   at SolarWinds.Orion.Core.CertificateUpdate.TlsConfiguration.IsEnabled(Negotiation neg)
   at SolarWinds.Orion.Core.CertificateUpdate.EnvironmentDetails.Collect(Boolean getAgentsCount)
   at SolarWinds.Orion.Core.CertificateUpdate.Md5CertificateUpdater.<.ctor>b__0()
   at SolarWinds.Orion.Core.CertificateUpdate.Md5CertificateUpdater.ApplyFixes()
   at SolarWinds.Orion.Core.CertificateUpdate.CertificateMaintenance.StartCertificateMaintenance()
   at SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerPlugin.ScheduleCertificateMaintenance()
   at SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerPlugin.Start()
   at SolarWinds.BusinessLayerHost.Contract.BusinessLayerPlugin.Start()
   at SolarWinds.BusinessLayerHost.PluginInstanceAppDomain.Start()

Environment

  • NPM 12 and earlier
  • Microsoft Windows Server 2008 or later

Cause 

The Core Business Layer is unable to start properly due to protocol requirements.

Resolution

  1. Go to Start > Run, and then enter regedit to open the Windows Registry Editor.
    Note: It is strongly recommended to create a backup of your registry as this could have detrimental effects to your computer if done incorrectly.
  2. Click and highlight Computer at the top of the registry tree. Click File > Export to backup the registry, and then select a file location to save the registry file.
  3. Browse to the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
  4. Use the following registry configuration:
    Notes:
    • To easily add (import) the registry entries, copy the content into Notepad or any other text editor, save as a registry file (extension .reg) and merge.
    • When saving, make sure to change the format to ANSI.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:ffffffff
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:ffffffff
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
"Enabled"=dword:00000001

 

Last modified
07:17, 25 Apr 2017

Tags

Classifications

Public