Submit a ticketCall us

WebinarFREE IT Monitoring Webcast

Don’t miss out on our webcast, Essential IT Monitoring with SolarWinds ipMonitor, where we will show you how to keep an eye on your IT environment from one centralized, affordable, and lightweight monitoring tool: SolarWinds® ipMonitor®.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Database configuration failed: Exception while configuring plugin Orion Core Services component

Database configuration failed: Exception while configuring plugin Orion Core Services component

Updated March 31st, 2016

Overview

When the Configuration wizard fails with the following message, review the troubleshooting and resolution steps in this article.

Database configuration failed: Exception while configuring plugin Orion Core Services component. An error occurred while getting the provider information from the database. This can be caused by Entity Framework using an incorrect connection string. Check the inner exceptions for details and ensure that the connection string is correct.

Environment

All NPM versions

Cause 

This database connection issue is caused by port 1433 not being able to associate the instance name to the Orion database SQL services.

Resolution

  1. Test the SQL connection from the Orion server using the same connection string used in the Configuration wizard either by SQL Server Management Studio or UDL connection:
  2. Verify if the database has Named Pipes enabled via SQL Server Configuration Manager on the SQL Server. For more information, see Configure a Server to Listen on an Alternate Pipe (SQL Server Configuration Manager) (© 2017 Microsoft, available at https://technet.microsoft.com, obtained on April 27, 2017.).
  3. If the database is on an instance or you see a connection string fail, such as in the configurationwizard.log files, make sure that the SQL browser is running for that database.

    For example:

    ERROR OrionMainPlugin - Caught SQL exception in stored procedure UpdateAccounts: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) : Exception details: System.Data.SqlClient.SqlError: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    For more information, see How to: Start and Stop the SQL Server Browser Service (© 2017 Microsoft, available at https://technet.microsoft.com, obtained on April 27, 2017.).

  4. If the database connection is using a named instance which is not the default database name then it may be necessary to append the port number: 1443 to the database name.

    If appending the port number using the colon is not working, try configuring the SQL server name with a comma, such as \\servername.domain.local\instancename,1433.

 

Related links

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified

Tags

Classifications

Public