April 27, 2016 at 6:20 pm
TCP/IP & NAMED PIPES enabled.
We get these errors once in a while when connecting from application.
---> System.Data.SqlClient.SqlException: 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) ---> System.ComponentModel.Win32Exception: The network path was not found.
System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not usable)
Please share your thoughts.
April 28, 2016 at 12:44 am
Are you still getting this error or it got resolved on next try?
April 28, 2016 at 3:50 am
This article describes the steps required to troubleshoot connectivity issues:
-- Gianluca Sartori
April 28, 2016 at 5:13 am
Still get these errors few times every day.
Should this be a firewall/network issue? Or is this a connection string issue?
April 28, 2016 at 6:55 am
So it's an intermittent failure, it's not consistently failing?
In this case, you should monitor the network on both sides (SQL Server and client) and see if you're experiencing some failures.
-- Gianluca Sartori
April 28, 2016 at 8:43 am
Thanks, it's intermittent failures. What network test can be done regarding this issue?
April 28, 2016 at 7:37 pm
Are you connecting to the server via name or IP? If by name try by IP address and see if you get the same issue.
April 28, 2016 at 11:04 pm
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply