At this time I do not know which client would want to connect.. especially
as in the mean-time I have deleted all SQL server instances on my developer
machine and have deleted the only SSL certificate on the local IIS. This is
my private server, with no other computers connected.
Now the installation of the default instance (the first instance) of SQL
Server 2000 aborts with the same SECDoClientHandshake()) as the excerpt from
the latter part of WINNT\sqlstp.log , i.e. the log that sql server creates
during installation, shows:
.....
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=P4;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
(SECDoClientHandshake()).
driver={sql server};server=P4;UID=sa;PWD=;database=master
......
and it ends with .."Setup failed..."
Could there be a setting in the registry remaining that makes it do an
additional security check, implemented by creating the SSL certificate?
Thank you.
PeterK
"Kevin McDonnell [MSFT]" wrote in message
> Sounds like the cert on the server is being read on startup.
>
> Client --->SQL/Reporting Serve/IIS
>
> Is this your scenario?
>
>
> Thanks,
>
> Kevin McDonnell
> Microsoft Corporation
>
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
> >> Stay informed about: SSL Security error -ConnectionOpen(SECDoClientHandshake)