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) > Schema Error after Upgrade

Schema Error after Upgrade

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

Views: 29 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