当我尝试连接SQL Server时，我得到以下错误:
在建立与SQL Server的连接时，发生了与网络相关或特定于实例的错误。未找到服务器或无法访问服务器。验证实例名称是否正确，SQL Server是否配置为允许远程连接。(提供商:Named Pipes提供商，错误:40 -无法打开到SQL Server的连接)
当我试图在Visual Studio 2010中将数据库配置为gridview时抛出此错误。我不知道如何调试这个错误。
如何调试此错误?除了错误消息中提到的步骤之外，我还应该采取哪些步骤来确定这里到底发生了什么?
当前回答
我通过打开服务来解决这个问题，然后开始运行Sql Server (Sqlexpress)服务。
其他回答
尝试在连接字符串的末尾添加一个和一个端口号(如1433)。
我尝试了关于这个问题的所有其他答案，其中一些(如果不是全部的话)可能在让这个为我工作方面发挥了作用，但我仍然无法远程连接到DB。我在Azure虚拟机上使用SQL Server。
我最终想起了VM的端点是由Azure帐户代理控制的，所以我继续使用Azure Portal并添加1433作为可用端点，这样我就可以连接到我的SQL实例了。
希望这能帮助那些尝试了所有其他答案但仍然没有运气的人!
如果SQL Server正在运行，您仍然得到一个错误; 当打开SQL Server时，显示的不是默认的服务器名 选项下选择以\SQLEXPRESS结尾的服务器名 服务器名称->浏览更多信息->数据库引擎选项。
我将使用Entity Framework的项目设置为启动项目，然后运行update-database命令，解决了这个问题。
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论坛的帖子帮助我找到了这个。
