透過Veeam將某一台SQL Server抄寫至異地,於異地開啟後,SQL Server Service無法啟用。
1.查詢c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\errorlog
查詢SQL Server的錯誤訊息,如下圖:
2.於網路上查2找相關訊息,參閱下方網頁
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3d51382e-09fc-4b02-9b1b-386abcdd0f94/couldnot-start-sql-services-sql-server-could-not-spawn-fruncm-thread?forum=sqlgetstarted
解決方式將 "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\SuperSocketNetLib\certificate的值清空,如下圖:
======================================================================
couldnot start SQL Services (SQL Server could not spawn FRunCM thread.)
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3d51382e-09fc-4b02-9b1b-386abcdd0f94/couldnot-start-sql-services-sql-server-could-not-spawn-fruncm-thread?forum=sqlgetstarted
You are loading the cetrtificate while starting SQL instance.
Make sure that at the registry location: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\MSSQLServer\SuperSocketNetLib\" has a valid thumbprint.
Have you been able to start the SQL instance with this certificate before? If you are not using the certificate anymore, please remove the certificact Key entry from the above registry location and start the instance.
For SQL Server 2005 to load a SSL certificate, the certificate must meet the following conditions:
- The certificate must be in either the local computer certificate store or the current user certificate store.
- The current system time must be after the Valid from property of the certificate and before theValid to property of the certificate.
- The certificate must be meant for server authentication. This requires the Enhanced Key Usageproperty of the certificate to specify Server Authentication (1.3.6.1.5.5.7.3.1).
- The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) will also include key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
- The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. If SQL Server is running on a failover cluster, the common name must match the host name or FQDN of the virtual server and the certificates must be provisioned on all nodes in the failover cluster.
沒有留言:
張貼留言