Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2018Jan2 - Deletes > Core Businesslayer crash in NPM 11.5.3 or SAM 6.2.3 for Specified cast is not valid

Core Businesslayer crash in NPM 11.5.3 or SAM 6.2.3 for Specified cast is not valid

Created by Adrian Cook, last modified by Gerald.Prado on Jan 02, 2018

Views: 938 Votes: 5 Revisions: 5

Overview

 

An issue can occur such as the Orion Module Engine ( Solarwinds Business layer) service may crash after upgrading to NPM 11.5.3 or SAM 6.2.3

 

You will find in the business layer host log file the following error,

 

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 11.5.3, SAM 6.2.3

Cause 

 

Orion protocol requirements

Resolution

  1. Start the Windows Registry Editor by clicking on Start and Run.

  2. Type in "regedit" into the Run field (without quotations).

  3. Highlight Computer at the top of the registry tree.  Backup the registry first by clicking on File and then on Export.  Select a file location to save the Registry file.

    Note: You will be editing the registry.  This could have detrimental effects on your computer if done incorrectly, so it is strongly advised to make a backup.

    Locate:
    HKEY
    _LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
  4. Remove the registry key for TLS 1.2 since it is not there by default and removing it should not cause any issues. Otherwise, add DisabledByDefault with a Value of 1 
  5. Restart the Orion services.

 

 

Last modified

Tags

Classifications

Public