Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Schema Error after Upgrade

Schema Error after Upgrade

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

Views: 22 Votes: 0 Revisions: 4

Overview

This article provides information on general Schema errors in the Configuration Wizard resolution steps.

 

Errors in the Information service logs:

2013-01-10 15:09:04,379 [19] ERROR SolarWinds.InformationService.Core.InformationService - Exception caught in method RunQuery
SolarWinds.Data.Query.EntityNotFoundException: Source entity [Orion.NPM.Schema] not found in catalog

 

Environment

NPM version 9.5 and later

 

Cause 

Schema conflicts in SWIS after an upgrade (usually with older versions of Core).

 

Resolution

1. Locate the ConfigurationWizard.exe.config and open it in a text editor. 
2. Locate the XML element <appSettings>.
3. Add <add key="Packaging.Internal.RepairMode" value="true"/> element into <appSettings> and then save file.
4. Stop all SolarWinds services and websites.
5. Run SolarWinds Configuration Wizard and select all three options here.
6. Set the key to false after Configuration Wizard has completed.

 

 

 

 

Last modified
23:31, 22 Jun 2016

Tags

Classifications

Public