HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLServer\SuperSocketNetLib HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib If you are using SQL Server 2005, you can find the Certificate registry entry under the following registry subkey:
Starting with Microsoft SQL Server 2000 Service Pack 1, SQL Server looks for a binary value that is named Certificate in this registry key:
If you deploy SQL Server with a failover cluster, you must install the server certificate with the FQDN of the virtual server on all nodes in the failover cluster. 15:12:09.74 server SQL Server could not spawn FRunCM thread.įor the SQL Server 2000 golden release, SQL Server looks at the certificate store to find a certificate with the same name as the Fully Qualified Domain Name System (FQDN) of the SQL Server computer name. 15:12:09.67 server Unable to load any netlibs. 15:12:09.62 server Could not set up Net-Library 'SSNETLIB'. 15:12:09.48 server Encryption requested but no valid certificate was found. If the computer that is running SQL Server to which the client is trying to connect does not have a certificate installed, the client receives this error message: Therefore, the client cannot connect to Microsoft SQL Server 6.5 or Microsoft SQL Server 7.0. If the Force Protocol Encryption option is turned on on the client, that client is no longer backward compatible. If that client tries to connect to another computer that is running SQL Server, the client tries to encrypt the communication. If the Force Protocol Encryption option is turned on on the client by using the SQL Server Client Network Utility, only communication for that client to SQL Server is encrypted.
A certificate is required because SSL encryption works only with instances of SQL Server 2000 that are running on a computer that has a certificate assigned from a public certification authority.įor more information, click the following article number to view the article in the Microsoft Knowledge Base:Ģ76553 How to enable SSL encryption for SQL Server 2000 with Certificate Serverįor more information about how to turn on SSL encryption for SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:ģ16898 How to enable SSL encryption for SQL Server 2000 with Microsoft Management Console When the Force Protocol Encryption is on, SQL Server uses Secure Sockets Layer (SSL) to encrypt all communication between the client and SQL Server. SQL Server 2000 supports the Force Protocol Encryption option to control the Net-Library encryption. More Information How SQL Server uses certificates
For more information, see the "How to: Enable Encryption Connections to the Database Engine (SQL Server Configuration Manager)" topic in SQL Server 2005 Books Online. You can set the value of the ForceEncryption option to Yes to enable encryption connections for an instance of SQL Server. However, in SQL Server 2005, use the ForceEncryption option instead of the Force Protocol Encryption option. Note The concepts and discussions in this article that apply to SQL Server 2000 also apply to SQL Server 2005. This article describes how SQL Server uses, locates, and validates a certificate when the Force Protocol Encryption option is turned on either on the client or on the server to enable Net-Library encryption. How SQL Server uses a certificate when the Force Protocol Encryption option is turned on Summary