Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Resolve "Database configuration failed" message that appears in Configuration Wizard after uninstalling SAM 6.7 and then reinstalling SAM with or without other Orion Platform products

Resolve "Database configuration failed" message that appears in Configuration Wizard after uninstalling SAM 6.7 and then reinstalling SAM with or without other Orion Platform products

Updated September 18, 2018

Overview

This article describes how to resolve a "Database configuration failed" message that may appear in the Configuration Wizard if you uninstall SAM 6.7 and then reinstall SAM either alone or with other Orion Platform products.

Additional messages displayed may include:

  • Failure importing sample map
  • Alerts Migration failed
  • Dependency Migration failed

Environment

  • SAM 6.7 or later
  • APM 1.0 or later

This issue impacts Orion Platform installations that include SAM 6.7 and the following products:

  • IPAM 4.7
  • NCM 7.8
  • NPM 12.3
  • NTA 4.4 and 4.5
  • Log Manager 1.1
  • SCM 1.0
  • UDT 3.3.1
  • VMAN 8.3
  • VNQM 4.5
  • WPM 2.2.2

Cause 

When SAM 6.7 is installed, the Orion Installer adds a package related to SolarWinds APM — SAM.AppOptics to C:\ProgramData\Solarwinds\InformationService\v3.0 for later use if you integrate SAM with SolarWinds APM.

If you uninstall SAM, the MSI application launched via the Windows Control Panel does not remove the SAM.AppOptics package. When you run the Orion Installer again to reinstall SAM, a "Database configuration failed" message appears if the remaining APM package blocks the loading of required entities.

Resolution

  1. Log into the Orion Server with administrator privileges.
  2. In a text editor, open the Orion.Installer.Packaging.root file stored in the C:\Program Files (x86)\SolarWinds\Orion\Packaging\Roots folder.
  3. Remove the following line (the version number will vary) and save the file:

<requires id="Orion.SAM.AppOptics" version="[1.0.0.867,]" /> 

  1. Run the Orion Configuration wizard to refresh files on the web server and check the database structure. 

 

Last modified

Tags

Classifications

Public