Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'SolarWindsOrionDatabaseUser'

System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'SolarWindsOrionDatabaseUser'

Created by Michael Perez, last modified by Alexander Aguilar on Feb 24, 2017

Views: 2,956 Votes: 2 Revisions: 7

Overview

Configuration Wizard fails and is showing the following error in the ConfigurationWizard.log:

System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'SolarWindsOrionDatabaseUser'

This issue usually happens when the account or password that Orion uses to contact to the database was changed during an upgrade, or new product installation.

Environment

All Orion products

Cause 

The Configuration Wizard is using the previous connection string to access the Orion database.  During additional installations or product upgrades, the option to change the username or password is no longer presented during the Configuration Wizard.  

Resolution

  1. Open regedit.exe
  2. Create a backup of the registry before making any changes - Importing or exporting Keys.
  3. Go to one of the following keys:

    On a 64 bit OS:  

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds.net\ConfigurationWizard\ConfiguredModules   

    On a 32 bit OS:  

    HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds.net\ConfigurationWizard\ConfiguredModules

  4. Delete all keys except for (Default).
  5. Run the Configuration Wizard again (Start > All Programs > SolarWinds Orion > Configuration and Auto-Discovery).
  6. Select Database, Website, and Services and click Next.
  7. Enter the correct credentials for the Orion database user and click Next.
  8. Select the Orion database and click Next.
  9. Enter the correct credentials for the Orion database and complete the remaining steps in the Configuration Wizard.

Note: If the above fails to resolve the issue make sure Named Pipes is enabled for the SQL server.

 

Last modified
09:06, 24 Feb 2017

Tags

Classifications

Public