SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
Change Is Inevitable
Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.
Learn more.
Updated September 19, 2018
Exception 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Connection string - Data Source=*SQL SERVER NAME*;Initial Catalog=*DB NAME*_Prod;User ID=*DB USER NAME*;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Application Name=SolarWinds.DataProcessor@domain-DataProcessorHost-0;Workstation ID=*MACHINE ID*
This error indicates that your physical server is not able to connect to SQL Server.
It is the most common error where your SQL Server is rejecting a connection form Outside. You might have incorrect Credentials to access the SQL server; therefore, the Configuration wizard is failing to connect to the database server.
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Please consult your DBA before making any changes.
Possible troubleshooting steps:
Make sure the SQL Server and SQL Server Browser services are running at all times on the server hosting your SQL instance.
The following screenshots are an example using SQL EXPRESS edition. The screenshots are a property of © 2016 Microsoft.
Make sure the SQL Server and SQL Server Browser services are running at all times on the server hosting your SQL instance.
You can also use third-party DB connectivity tools to check if you are able to reach out to SQL server.
To quickly test a database connection, try the Database Connection String / Command / SQL Tester Utility:
Learn more:
Download details: Microsoft® SQL Server® 2008 Management Studio Express - Microsoft Download Center (© 2016 Microsoft, available at https://www.microsoft.com, obtained on December 8, 2016)
Once Done, follow the instructions in the following post. Make sure you are able to connect to SQL Server using SQL Studio.
How to enable remote connections in SQL Server 2008?
(© 2016 Microsoft, available at https://blogs.msdn.microsoft.com, obtained on January 16, 2017)
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.
SUGGESTED TAGS: List below the tags you think should be added to make this article easy to find by a user. Include product, version/release (if it only applies to specifics releases etc.
network-related or instance-specific error occurred while establishing a connection to SQL Server, Named Pipes Provider, error: 40 - Could not open a connection to SQL Server