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) > Configuration Wizard: Cannot add index (PK_configwizardlog)

Configuration Wizard: Cannot add index (PK_configwizardlog)

Created by Giane Ira, last modified by Mariusz Handke on Nov 03, 2016

Views: 2,086 Votes: 3 Revisions: 12

Overview

An error similar to the following appears during Configuration Wizard:

Cannot add index (PK_ConfigWizardLog)

Environment

All NPM versions

Cause 

  • The database has reached the size limit.
  • There are incomplete permissions for the SQL account.
  • Duplicate rows (duplicate LogID values) in ConfigWizardLog table

Resolution

Log into the database and verify that there is available space.
If the database is full, create space by truncating the following:

  1. Open the Syslog table and run Truncate Table Syslog.
  2. Open the Traps table and run Truncate Table Traps.
  3. Open the TrapVarbinds table and run Truncate Table TrapVarbinds.

If disk space is not the issue,

  1. Make sure the SQL account being used has the dbcreator, db_owner and securityadmin permissions.

    2. Re-run the Configuration Wizard.

 

If the error persists after doing all of the above run the following SQL command to drop the Configwizardlog table MAKE SURE YOU HAVE A DB BACKUP

- Drop table dbo.configwizardlog

 

Preferable approach, in order to retain logs, would be to find duplicate rows in the ConfigWizardLog table and remove duplicates. Below query will list LogID values which have duplicates:

SELECT LogID
FROM [dbo].[ConfigWizardLog]
GROUP BY LogID
HAVING (COUNT(LogID) > 1)

Note: To copy content without line numbers, hover over the text and click the view source button (View Source). This opens a new window where you can select and copy text without any formatting or line numbering.

 

 

Below query will list complete rows, with time-stamps, to help you decide which rows to delete:

SELECT *
FROM [dbo].[ConfigWizardLog]
WHERE LogID IN (
SELECT LogID
FROM [dbo].[ConfigWizardLog]
GROUP BY LogID
HAVING (COUNT(LogID) > 1)
)

Note: To copy content without line numbers, hover over the text and click the view source button (View Source). This opens a new window where you can select and copy text without any formatting or line numbering.

 

Last modified

Tags

Classifications

Public