当我尝试连接SQL Server时，我得到以下错误:
在建立与SQL Server的连接时，发生了与网络相关或特定于实例的错误。未找到服务器或无法访问服务器。验证实例名称是否正确，SQL Server是否配置为允许远程连接。(提供商:Named Pipes提供商，错误:40 -无法打开到SQL Server的连接)
当我试图在Visual Studio 2010中将数据库配置为gridview时抛出此错误。我不知道如何调试这个错误。
如何调试此错误?除了错误消息中提到的步骤之外，我还应该采取哪些步骤来确定这里到底发生了什么?
当前回答
尝试在连接字符串的末尾添加一个和一个端口号(如1433)。
其他回答
当我想在另一台PC上运行我的WinForms项目(包括使用SQL Server数据库，并且在我的PC上工作得很好)时，我也犯了同样的错误。问题出在我电脑的Windows防火墙上。我通过添加两条规则来解决这个问题。这是如何允许SQL Server通过Windows防火墙的整个过程:
打开“运行”，输入services.msc 查找用于SQL Server(实例名)和SQL Server Browser的服务。一次一个，右键单击，选择“属性”，复制路径到exe文件 然后打开防火墙。cpl，单击允许应用程序或添加规则，添加之前复制的路径(有一个步骤需要遵循)，选中域和私有，取消选中公共。
这是YouTube的链接，你可以看到这个过程:允许SQL Server通过Windows防火墙
即使我使用了正确的凭证，我也面临着这种问题。请务必执行以下操作。
确保您的sql server凭据。在sql server字段中，您必须使用计算机名。
要找到计算机名称，在您的计算机上搜索计算机名称，然后就可以找到计算机名称。然后粘贴并尝试连接。
如果无法正常工作，请尝试从服务启动计算机上的sql server。下面的截图会有帮助。
我发现以下技巧很有用:
Make sure your database engine is configured to accept remote connections: Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration Click on Surface Area Configuration for Services and Connections Select the instance that is having a problem > Database Engine > Remote Connections Enable local and remote connections Restart instance You may need to create an exception on the firewall for the SQL Server instance and port you are using: Start > Run > Firewall.cpl Click on exceptions tab Add sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Bin, check your installs for the actual folder path) and port (default is 1433) Check your connection string as well From FIX : ERROR : Could not open a connection to SQL Server: Check if your SQL server services is up and running properly: Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > SQL Server Services Check to make sure SQL Server service status is Running. In addition, ensure that your remote server is in the same network. Run sqlcmd -L to ascertain if your server is included in your network list. Enable TCP/IP in SQL Server Configuration When two or more SQL Servers are connected across network they do all communication using TCP/IP. The default port of SQL Server installation is 1433. This port can be changed through SQL Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected. Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP Right Click on TCP/IP >> Click on Enable You must restart SQL Server Services for all the changes to take effect. Right click and go to menu properties to select location where default port of SQL Server can be changed.
I had the same issue after upgrading my Windows to Windows Pro 10 21H2. I have two SQL instances - 2014 and 2019 and I was not able to connect only to 2019 one. I restarted the computer, restarted all SQL related services. Two of the services were showing errors (SQL Server and SQL Server agent) and I was not able to start them. I could not also start these two services from C:\Windows\SysWOW64\SQLServerManager15.msc In the logs (C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER01\MSSQL\Log) I saw these lines:
Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 0.
Error: 17190, Severity: 16, State: 1.
Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
原来在升级后，服务的“Log On”属性(服务属性上的第二个选项卡)被设置为NT AUTHORITY\NETWORK SERVICES。当我将其更改为“本地系统帐户”时，我能够启动服务并连接到MS SQL 2019实例。
这个msdn论坛的帖子帮助我找到了这个。
如果你使用的是快速版:
您需要在服务器名称后添加\SQLEXPRESS
例如我的服务器\ SQLEXPRESS
