Network Management
NCM: "You currently cannot connect to the 'XX' server either because the server is not yet upgraded to version XXXX or there is a problem on your network."
This article discusses the steps on how to resolve the error of the NCM page as follows: "You currently cannot connect to the 'XX' server either because the server is not yet upgraded to version XXXX or there is a problem on your network."
First published date
3/24/2020 2:11 AM
Last published date
5/30/2023 1:39 PM
Overview
NCM pages display error messages: "You currently cannot connect to the 'XX' server either because the server is not yet upgraded to version XXXX or there is a problem on your network."
From the following logfile "NcmBusinessLayerPlugin.log", you will see the following error:
From the following logfile "NcmBusinessLayerPlugin.log", you will see the following error:
[Main] ERROR SolarWinds.Orion.Common.SWEventLogging - Unhandled Exception caught in Core Service Engine startup.
Invalid object name 'dbo.NCM_BaselineNodeMap'.
[Main] FATAL SolarWinds.NCM.BusinessLayerPlugin.NcmBusinessLayerPlugin - Unhandled Exception caught in plugin
startup.System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'dbo.NCM_BaselineNodeMap'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)Product section
Network Configuration Manager
Cause
- NCM Business Layer is not running
- Duplicate Primary Poller entries in Engines table
Resolution
Scenario 1: Main in High availability (HA) Pool: If you have Main Pollers in High availability (HA) configuration and there was fail over incident which resulted in both Main Pollers showing active / standby, then you may notice this errors because the Engines table has duplicate Primary Pollers.
- To fix this Remove the Primary Poller entry that is Standby
- Verify HA Roles are correctly set for both Servers and SolarWinds services status are set accordingly
Scenario 2: No High availability (HA)
If your environment does not have High availability (HA) and on 2022.x or later SolarWinds Platform, the NCM module is located in the SolarWinds Platform, repair SolarWinds Platform or Observability via Control Panel > Programs and Features then finish configuration wizard.
- Another Workaround is to remove the Widget and placed or moved the same resource instead to the NCM Summary Page.(consult support before doing this step)
- To fix this Remove the Primary Poller entry that is Standby
- Verify HA Roles are correctly set for both Servers and SolarWinds services status are set accordingly
Scenario 2: No High availability (HA)
If your environment does not have High availability (HA) and on 2022.x or later SolarWinds Platform, the NCM module is located in the SolarWinds Platform, repair SolarWinds Platform or Observability via Control Panel > Programs and Features then finish configuration wizard.
- Another Workaround is to remove the Widget and placed or moved the same resource instead to the NCM Summary Page.(consult support before doing this step)