error: 40 - Could not open a connection to SQL Server

K. MOHANA PRIYA 61 Reputation points
2020-08-31T09:12:41.203+00:00

I am getting an Exception Unhandled error.

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)'

Inner Exception
Win32Exception: The network path was not found.

It show that check the server allow to remote connection and the instance. I checked the connection and also the instance all are correct.
Anyone tell me how to solve it.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Uri Dimant 211 Reputation points
    2020-09-02T02:15:37.037+00:00
    1. Make sure SQL Server Service is running
    2. If a named instance, make sure SQL Server browser service is running
    3. Make sure SQL Server is configured to allow remote connections
    4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
    5. Test server connectivity with PING from the client machine
    6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
      a. TELNET <server-name> 1433
      b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$)) "server listening on TCP port $" }
    7. Check firewall settings if step 5 or 6 connectivity test fails

    Was this answer helpful?

    1 person found this answer helpful.
  2. Pai Manoor, Deepthi 0 Reputation points
    2024-01-30T20:31:57.32+00:00

    SQL terminal error 35 & 40: Drop container: docker rm sql Then rerun the Code: docker run -e ACCEPT_EULA=1 -e MSSQL_SA_PASSWORD={password} -e MSSQL_PID=Developer -e MSSQL_USER=SA -p 1433:1433 -d --name=sql mcr.microsoft.com/azure-sql-edge

    Was this answer helpful?

  3. NOBTA 86 Reputation points
    2020-09-02T15:12:44.727+00:00

    You may check whether TCP/Named pipes setting is enabled on SQL Server if you use SQL Server Developer Edition. The default setting of TCP/Named pipes is disable on SQL Server Developer Edition. You can change this setting using SQL Server configuration manager. And also you may check firewall configured for incoming connections on Windows OS.

    https://learn.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager?view=sql-server-ver15#manage-server--client-network-protocols

    Was this answer helpful?

    0 comments
  4. SQLZealots 276 Reputation points
    2020-09-02T02:26:33.583+00:00

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.