0
SQL Server 2014 Express運行良好,但不知道週末突然發生了什麼,它並未啓動。我試圖手動運行它,但它拋出錯誤信息。SQL Server 2014 Express突然停止工作,並且沒有起牀
錯誤日誌文件如下:
2017-04-10 10:36:41.56 spid9s Starting up database 'msdb'.
2017-04-10 10:36:41.56 spid12s Starting up database 'mssqlsystemresource'.
2017-04-10 10:36:41.57 spid12s The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2017-04-10 10:36:41.59 spid9s 1 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2017-04-10 10:36:41.60 spid9s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2017-04-10 10:36:41.60 spid12s Starting up database 'model'.
2017-04-10 10:36:41.63 spid12s Clearing tempdb database.
2017-04-10 10:36:41.76 spid12s Starting up database 'tempdb'.
2017-04-10 10:36:41.92 spid14s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid.
2017-04-10 10:36:41.92 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2017-04-10 10:36:41.92 spid14s Error: 17182, Severity: 16, State: 1.
2017-04-10 10:36:41.92 spid14s TDSSNIClient initialization failed with error 0x80090331, status code 0x80. Reason: Unable to initialize SSL support. The client and server cannot communicate, because they do not possess a common algorithm.
2017-04-10 10:36:41.92 spid14s Error: 17182, Severity: 16, State: 1.
2017-04-10 10:36:41.92 spid14s TDSSNIClient initialization failed with error 0x80090331, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The client and server cannot communicate, because they do not possess a common algorithm.
2017-04-10 10:36:41.92 spid14s Error: 17826, Severity: 18, State: 3.
2017-04-10 10:36:41.92 spid14s 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.
2017-04-10 10:36:41.92 spid14s Error: 17120, Severity: 16, State: 1.
2017-04-10 10:36:41.92 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
我試圖谷歌,但沒有得到任何修復。我不想使用任何自定義SSL證書或SQL Server的任何高端功能。我只是想用它從我的應用程序收集數據。使用存儲過程進行簡單的CRUD操作。任何人都可以幫助我理解SQL服務器有什麼問題。任何解決方法也將工作。
下載你可能已經嘗試過了,但我必須問。你嘗試卸載並重新安裝sql服務器? – GuidoG
@GuidoG是的,我試圖做到這一點,並嘗試修復,但四小時後沒有運氣。 –
你可以試試[this](https://connect.microsoft.com/SQLServer/feedback/details/330614/sql-server-could-not-spawn-fruncm-thread)和[this](http:// stackoverflow .com/questions/15230581/cant-get-sql-server-to-start-or-connect-to-my-local-database-engine-through-ssm),可能有幫助 – TheGameiswar