Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Ignoring discovery interface xxx failed

Ignoring discovery interface xxx failed

Created by Vladimir.Bubenik, last modified by Rodim Suarez_ret on Mar 29, 2017

Views: 294 Votes: 0 Revisions: 8


This article describes an issue where you receive the following error message:

Ignoring discovery interface [name of interface] failed







The Core.BusinessLayer.log is showing the following errors related to failed import:

<Processing of discovery result for profile 35 failed for plugin SolarWinds.Orion.Core.DiscoveryPlugin.CoreDiscoveryPlugin
System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_DiscoveredNodePortMaps'. Cannot insert duplicate key in object 'dbo.DiscoveredNodePortMaps'. The duplicate key value is (35, 2, 1, 0).>


All NPM versions




Note: Create a backup the database before making any changes.

  1. Go to Start > SolarWinds Orion > Advanced Features > Database Manager.
  2. Locate your SolarWinds Orion database then click Add default server.
  3. Right click your SolarWinds Orion database and select New Query.
  4. Paste the following query and click on Execute:
TRUNCATE TABLE DiscoveredNodePortMaps;


Last modified