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) > Invalid column name DeletedOn

Invalid column name DeletedOn

Created by Jane Baylon, last modified by Alexander Aguilar on Dec 15, 2016

Views: 101 Votes: 0 Revisions: 4

Updated: July 18, 2016

Overview

This article describes the issue when you receive this error message in the Configuration Wizard which fails due to invalid columns in IPAM table. Sample error in Configuration Wizard log shown below:

2016-07-14 13:33:02,396 [10] ERROR ConfigurationProgressScene - Error while executing script- Invalid column name 'DeletedOn'.
SolarWinds.ConfigurationWizard.Common.ConfigurationException: Error while executing script- Invalid column name 'DeletedOn'.
   at SolarWinds.ConfigurationWizard.Plugin.Common.DBConfigProcessor.ExecuteSqlBatch(IDbConnection connection, String sqlQuery, ConfigurationLogDelegate configLog)
   at SolarWinds.ConfigurationWizard.Plugin.Common.DBConfigProcessor.Process(IDbConnection connection, ConfigurationProgressDelegate progress, String scriptFile, ConfigurationLogDelegate logger)
   at SolarWinds.ConfigurationWizard.Plugin.Common.ModuleHelper.ConfigureDatabase(IOrionConfigHost host, ConfigurationProgressDelegate progress, ConfigurationLogDelegate logger, String dbStructureFile, String dbConfigFile, String initialWebConfigFile)
   at SolarWinds.ConfigurationWizard.Plugin.IPAM.IPAMMainPlugin.ConfigureDatabase(IOrionConfigHost host, ConfigurationProgressDelegate progress, ConfigurationLog

Environment

  • NPM 11.5.x
  • IPAM 4.x

 

Cause 

This is due to invalid columns in the IPAM tables.

 

Resolution

Note: Before doing any work on your database please make sure that you have a current backup as this will make a permanent change to your database. 

  1. Open SQL Management Studio and connect to your Orion database.
  2. Run the query simultaneously:

DROP TABLE IPAM_CONFLICT

DROP TABLE IPAM_CONFLICTDATA

  1. Click Execute Query.

 

 

Last modified
07:59, 15 Dec 2016

Tags

Classifications

Public