SQL Server一直运行良好但从星期五开始我无法连接到SSMS中的数据库引擎。这恰好是我在Windows更新期间关闭笔记本电脑的原因，因为它似乎悬挂（我不知道这两者是否相关）。

从那以后我有：

• 在更新失败之前返回到还原点
• 从我的计算机中删除了SQL Server 2008
• 将SQL Server 2012安装到我的计算机上。这在加载期间失败
• 从我的机器中删除了标记为SQL Server的所有内容
• 重做失败的Windows更新
• 已安装的SQL Server 2012在加载时再次失败
• 创建了自签名证书（http://technet.microsoft.com/en-us/library/cc753127(v=WS.10).aspx）
• 试图从服务和SSCM启动SQL Server没有运气
• 尝试了SQL Server的各种登录选项 - 在本地系统下服务将启动但我仍然无法连接到SSMS中的数据库引擎
• 阅读无尽的帖子和文章

任何人都可以帮助我在我的机器上启动SQL Server，然后使用SSMS连接到数据库引擎吗？

安装的故障日志提供了以下信息：

2013-03-05 12:17:37.34 Server  Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)  Dec 28   2012 20:23:12  Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)  
2013-03-05 12:17:37.34 Server  (c) Microsoft Corporation.  
2013-03-05 12:17:37.34 Server  All rights reserved.  
2013-03-05 12:17:37.34 Server  Server process ID is 5116.  
2013-03-05 12:17:37.34 Server  System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: 'RV411/RV511/E3511/S3511/RV711'.  
2013-03-05 12:17:37.34 Server  Authentication mode is WINDOWS-ONLY.
2013-03-05 12:17:37.34 Server  Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.  
2013-03-05 12:17:37.34 Server  The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.  
2013-03-05 12:17:37.35 Server  Registry startup parameters:   
 -d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf    
 -e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG    
 -l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf  
2013-03-05 12:17:37.35 Server  Command Line Startup Parameters:    
 -s "MSSQLSERVER"
 -m "SqlSetup"
 -Q
 -q "Latin1_General_CI_AS"
 -T 4022
 -T 4010
 -T 3659
 -T 3610
 -T 8015
 -T 902
2013-03-05 12:17:37.69 Server  SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing.  This is an informational message; no user action is required.  
2013-03-05 12:17:37.69 Server  SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.  
2013-03-05 12:17:37.69 Server  Detected 6004 MB of RAM. This is an informational message; no user action is required.  
2013-03-05 12:17:37.69 Server  Using conventional memory in the memory manager.  
2013-03-05 12:17:38.02 Server  Perfmon counters for resource governor pools and groups failed to initialize and are disabled.  
2013-03-05 12:17:38.73 Server  Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.  
2013-03-05 12:17:38.75 Server  Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.  
2013-03-05 12:17:38.75 Server  Database Mirroring Transport is disabled in the endpoint configuration.  
2013-03-05 12:17:38.76 Server  Software Usage Metrics is disabled.  
2013-03-05 12:17:38.92 spid4s  Warning
 ******************  
2013-03-05 12:17:38.92 spid4s  SQL Server started in single-user mode. This an informational message only. No user action is required.
2013-03-05 12:17:39.07 spid4s  Starting up database 'master'.  
2013-03-05 12:17:39.66 Server  CLR version v4.0.30319 loaded.  
2013-03-05 12:17:40.35 spid4s  SQL Server Audit is starting the audits. This is an informational message. No user action is required.  
2013-03-05 12:17:40.38 spid4s  SQL Server Audit has started the audits. This is an informational message.  No user action is required.  
2013-03-05 12:17:41.33 spid4s  SQL Trace ID 1 was started by login "sa".  
2013-03-05 12:17:41.60 spid4s  Server name is 'E2E-LAPTOP'. This is an informational message only. No user action is required.  
2013-03-05 12:17:41.82 spid12s Password policy update was successful.  
2013-03-05 12:17:41.87 spid12s Error: 17190, Severity: 16, State: 1.  
2013-03-05 12:17:41.87 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.  
2013-03-05 12:17:41.87 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.  
2013-03-05 12:17:42.00 spid12s Error: 17182, Severity: 16, State: 1.  
2013-03-05 12:17:42.00 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.  
2013-03-05 12:17:42.00 spid12s Error: 17182, Severity: 16, State: 1.  
2013-03-05 12:17:42.00 spid12s 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.  
2013-03-05 12:17:42.00 spid12s Error: 17826, Severity: 18, State: 3.  
2013-03-05 12:17:42.00 spid12s 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.  
2013-03-05 12:17:42.00 spid12s Error: 17120, Severity: 16, State: 1.
2013-03-05 12:17:42.00 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

2013年3月7日：我现在已经通过在一台闪亮的新Windows 8笔记本电脑上安装SQL Server来解决这个问题（使用与我在错误机器上尝试的完全相同的过程）。当我有能量时，我会回来看看我能否在其他机器上解决这个问题。如果我有任何成功，我会更新这篇文章。