sql server connect: I am running SQL Server 2000 Developer (with Service Pack 3a) on
Windows XP Professional. After installing Windows XP Service Pack 2,
I can no longer connect to SQL Server. From Enterprise Manager, the
error shows up in a dialog when I click on the
"Machinename\Machinename (Windows NT)" node:

SQL Server Enterprise Manager
A connection could not be established to MACHINENAME\MACHINENAME
Reason: SSL Security Error
ConnectionOpen (SECDoClientHandshake())..
Please verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the
MACHINENAME\MACHINENAME node) and try again.

From the command line, the error is:

C:\>osql -E -S machinename\machinename
[DBMSLPCN]SSL Security error
[DBMSLPCN]ConnectionOpen (SECDoClientHandshake()).

This instance is configured as a named instance, with mixed-mode
authentication. I can't connect with either authentication modes. In
Windows Firewall, I tried both adding an exception for port 1433 and
turning it off, but the problem still exists. I can stop/start the
SQL server instance, but I can't connect to it.

I noticed in another thread comments about uninstalling certificate
services, but WinXP does not have certificate services or even DNS.
On this computer, I am running IIS 5.1. Also, I have used the
selfssl.exe utility (from IIS 6 administrators kit) to automatically
install a self-signed certificate. Maybe this has interacted somehow
with XP Service Pack 2.

I also tried making a UDL file with the OLE DB Provider for SQL
Server, making sure the "Use Encryption for Data" setting is set to

Never mind, the problem is solved. I followed the directions in KB
309398.

"PRB: SQL Server 2000 Installation or Local Connections Fail with "SSL
Security error :ConnectionOpen (SECDoClientHandshake())" Error Message"

http://support.microsoft.com/default.aspx?scid=kb;en-us;309398

After going through the procedure outlined, instead of reimporting the
certificates back into the "Certificates (Local
Computer)->Personal->Certificates" store, I just deleted them because
they are test certificates only. Then, I ran SelfSSL.exe again to
create a new certificate (with option /v:3650 so it will be valid for
10 years instead of default 7 days) and automatically assign it to my
default web site. Now, IIS works with SSL, and I can connect to SQL
Server.

What law is it again where your computer works fine right up until the
moment your client calls and you need to show them something,
whereupon it gives some bizarre error message? Murphy's law? Maybe