Orion losing connectivity with SQL server generating events provider: Named Pipes Provider, error - Could not open a connection to SQL Server

5/6/2019 7:58 PM

4/26/2023 10:26 PM

This article will explain the possible root cause when you have intermittent events within SolarWinds application server.

Events and application losing connectivity with SQL database.

This can be seen frequently under Event Viewer (Solarwinds)

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)


 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)


SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Orion Platform

Application Server performance 

SQL Server performance / Very Large Orion DB Maintained 

Layer 2/3 Latency Issues 

• Try to Restart the Orion Services: Start, Stop, or Restart Orion Services with the Orion Service Manager
• Please make sure you have proper setup hardware with MINIMUM Solarwinds requirements meeting on each poller.

This KB post is great place to start: What to check when the Orion website and server are very slow or there is a CPU and memory spike

• Make sure you have all the areas correctly configured and have the required hardware to run the Solarwinds application. 

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.

• You might have an issues within the SQL Server performance where you maintained very large Orion DB Maintained 

Quick Orion database health check guide This KB post will help you to understand and improve performance within the SQL server and maintaining the Orion DB.

• Layer 2/3 Latency Issues 

If you would like to monitor the connection and performance of your SQL Server, please consider one of our additional products DPA or SQL Sentry.