Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > Error: Database configuration failed Exception while configuring plugin Orion Core Services component Orion Database. There is already an object named 'XXX'

Error: Database configuration failed Exception while configuring plugin Orion Core Services component Orion Database. There is already an object named 'XXX'

Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 172 Votes: 2 Revisions: 8

Overview

This article explains a common Configuration wizard error that happens when there is some sort of table modification or migration as well as permissions of database user used during the run of the Configuration Wizard.

Environment

All versions of Orion products

 

Causes

This error occurs due to the following reasons:

  • Schema Mismatch
  • Versioning Mismatch
  • Botched Update or possible execute of a downgrade
  • SQL Permissions 'Less likely'

Resolution

Permissions of user in the configuration wizard:

The permissions may be modified or do not exist for the user on the database as it could have changed due to migration or audit of SQL.

To fix this, you need to troubleshoot the permissions issue to the database.

Note: Database owner's database role is required to connect but in some cases, you need a Server Role of Sys Admin to modify or create new tables (this is a case depending on how security intense SQL permissions are set).

You can check the roles in either logins or Security folder in SQL management studio.

 

  1. Right-click Account, and then click Properties.

'

 

  2.  Click Logins > Server Roles.

  3.  Right-click Account, and then go to Properties.

 

4. Click OK.

 

It is likely that there will be an error in the Configuration Wizard logs or in the error output of the Configuration Wizard UI. An example of a similar error message is shown below:

There is already an object named 'InterfaceTraffic_Detail_Trigger' in the database.

                                               

To fix this, create Trigger [InterfaceTraffic_Detail_Trigger] on [InterfaceTraffic_Detail]

     Instead of Insert

     as

     Insert Into [InterfaceTraffic_Detail]

     Select * from inserted

There is already an object named InterfaceTraffic_Hourly_Trigger in the database.

 

These examples show that it is unable to create a Trigger located on the Interface_Detail view table. Views cannot be seen from the Orion Database Manger tool and can only be seen from SQL management Studio https://msdn.microsoft.com/en-us/lib.../ms166547.aspx:

 

Note: Before making any changes, make sure to have a backup of the database. 

 

 

Last modified
22:15, 22 Jun 2016

Tags

Classifications

Public