Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Upgrade error: Violation of PRIMARY KEY constraint 'PK_NCM_RouteTable'. Cannot insert duplicate key in object 'dbo.NCM_RouteTable'. The statement has been terminated.

Upgrade error: Violation of PRIMARY KEY constraint 'PK_NCM_RouteTable'. Cannot insert duplicate key in object 'dbo.NCM_RouteTable'. The statement has been terminated.

Created by Mariusz Handke, last modified by Kevin.Swinson on Nov 09, 2017

Views: 690 Votes: 1 Revisions: 8

Updated April 9th, 2017

Overview

The following error appears when upgrading or migrating to NCM version 7.3 or later:

Violation of PRIMARY KEY constraint 'PK_NCM_RouteTable'. Cannot insert duplicate key in object 'dbo.NCM_RouteTable'. The statement has been terminated.

Environment

NCM 7.3 or later

Cause

There were changes in the NCM database schema in v7.3.

Resolution

As a workaround, skip the migration of the inventory data.

Warning: These steps will modify the Windows Registry. Make sure to backup your registry prior to making any changes.

  1. Open the command prompt on the NCM host.
  2. Execute one of the following commands:
  •  For 32 bit system:
reg add "HKLM\Software\SolarWinds.Net\Configuration Manager\Settings" /v DataToMigrate /t REG_SZ /d 3;1
  • For 64 bits system: 
reg add "HKLM\Software\Wow6432Node\SolarWinds.Net\Configuration Manager\Settings" /v DataToMigrate /t REG_SZ /d 3;1
  1. When prompted, type Y to overwrite the existing key.
  2. Restart the Orion Module Engine by going to Windows Services to initiate migration process again.

 

 

Last modified

Tags

Classifications

Public