Very Computer

I recently started to get error messages that look like this

SSL Security error
ConnectionOpen (SECDoClientHandshake())

That made me completely unable to connect to my SQL server. The messages
come up when I try to connect through the Enterprise Manager or through the
ODBC applet or through the coldfusion pages that use the ODBC connection.

The only error in the Window's log is this warning that appears once in the
Application log

MSSQLServer Event ID 19011
SuperSocket info (SpnRegister): Error 1355

--------------

I've tried reinstalling the SQL server but it hangs when it says it is
"starting and configuring the server" and puts the same error in the setup
log:

22:57:59 K:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe  -F
"K:\WINNT\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
"SQL_Latin1_General_CP1_CI_AS" -H 197126 -U sa -P
############################################################################
###

Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=YAHWEH;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=YAHWEH;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=YAHWEH;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
(SECDoClientHandshake()).

SQL Server configuration failed.

############################################################################
###

23:00:16 Process Exit Code: (-1)

--------------------

It all appears to be some sort of SSL issue. Aside from being an sql server
the machine is also a root CA, so perhaps that is involved. Really I have no
need to use an SSL connection to the server since I am only connecting from
a local machine and I am not really concerned about security in this case.
Interestingly enough the same SSL error seems to occur when I connect via
named pipes instead of TCP/IP. I was not aware that SSL could be used over
anything besides TCP/IP. I would really just like to get the server running.
I have no need for this SSL business.

in either client network utility or server network utility on the server
someone has set the "force protocol encryption" option on and you don't have
a certificate installed in the fully qualified DNS name of the server that's
valid for SSL.  The SPN error is totally unrelated.

There is a known issue with SSL encryption being turned on and certificate
services being on the same server - this is fixed in SQL 2000 SP1.  You can
call product support to get a hotfix...

--
Richard Waymire, MCDBA, MCSE

Quote:> I recently started to get error messages that look like this

> SSL Security error
> ConnectionOpen (SECDoClientHandshake())

> That made me completely unable to connect to my SQL server. The messages
> come up when I try to connect through the Enterprise Manager or through
the
> ODBC applet or through the coldfusion pages that use the ODBC connection.

> The only error in the Window's log is this warning that appears once in
the
> Application log

> MSSQLServer Event ID 19011
> SuperSocket info (SpnRegister): Error 1355

> --------------

> I've tried reinstalling the SQL server but it hangs when it says it is
> "starting and configuring the server" and puts the same error in the setup
> log:

> 22:57:59 K:\Program Files\Microsoft SQL

erver\80\Tools\Binn\cnfgsvr.exe  -F

Quote:> "K:\WINNT\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
> "SQL_Latin1_General_CP1_CI_AS" -H 197126 -U sa -P

############################################################################

Quote:> ###

> Starting Service ...

> SQL_Latin1_General_CP1_CI_AS

> -m -Q -T4022 -T3659

> Connecting to Server ...

> driver={sql server};server=YAHWEH;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=YAHWEH;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=YAHWEH;UID=sa;PWD=;database=master

> [Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error

> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
> (SECDoClientHandshake()).

> SQL Server configuration failed.

############################################################################

Quote:> ###

> 23:00:16 Process Exit Code: (-1)

> --------------------

> It all appears to be some sort of SSL issue. Aside from being an sql
server
> the machine is also a root CA, so perhaps that is involved. Really I have
no
> need to use an SSL connection to the server since I am only connecting
from
> a local machine and I am not really concerned about security in this case.
> Interestingly enough the same SSL error seems to occur when I connect via
> named pipes instead of TCP/IP. I was not aware that SSL could be used over
> anything besides TCP/IP. I would really just like to get the server
running.
> I have no need for this SSL business.

\Tools\Binn\cnfgsvr.exe  -F

Quote:> "K:\WINNT\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
> "SQL_Latin1_General_CP1_CI_AS" -H 197126 -U sa -P

###########################################################################
#

Quote:> ###

> Starting Service ...

> SQL_Latin1_General_CP1_CI_AS

> -m -Q -T4022 -T3659

> Connecting to Server ...

> driver={sql server};server=YAHWEH;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=YAHWEH;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=YAHWEH;UID=sa;PWD=;database=master

> [Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error

> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
> (SECDoClientHandshake()).

> SQL Server configuration failed.

###########################################################################
#

Quote:> ###

> 23:00:16 Process Exit Code: (-1)

> --------------------

> It all appears to be some sort of SSL issue. Aside from being an sql
server
> the machine is also a root CA, so perhaps that is involved. Really I
have no
> need to use an SSL connection to the server since I am only connecting
from
> a local machine and I am not really concerned about security in this
case.
> Interestingly enough the same SSL error seems to occur when I connect via
> named pipes instead of TCP/IP. I was not aware that SSL could be used
over
> anything besides TCP/IP. I would really just like to get the server
running.
> I have no need for this SSL business.

--
Posted via CNET Help.com
http://www.help.com/

Greetings,
   Are you aware that the transliteration of the Name of our Heavenly
Father and Creater ('YAHWEH') is in what you have posted? I have a website
with MANY LINKS to those that "make mention of" the Name YAHWEH at:
http://scroll.to/YAHshua .

Franklin Eugene Rhoads

\Tools\Binn\cnfgsvr.exe  -F

Quote:> "K:\WINNT\sqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q
> "SQL_Latin1_General_CP1_CI_AS" -H 197126 -U sa -P

###########################################################################
#

Quote:> ###

> Starting Service ...

> SQL_Latin1_General_CP1_CI_AS

> -m -Q -T4022 -T3659

> Connecting to Server ...

> driver={sql server};server=YAHWEH;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=YAHWEH;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=YAHWEH;UID=sa;PWD=;database=master

> [Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error

> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
> (SECDoClientHandshake()).

> SQL Server configuration failed.

###########################################################################
#

Quote:> ###

> 23:00:16 Process Exit Code: (-1)

> --------------------

> It all appears to be some sort of SSL issue. Aside from being an sql
server
> the machine is also a root CA, so perhaps that is involved. Really I
have no
> need to use an SSL connection to the server since I am only connecting
from
> a local machine and I am not really concerned about security in this
case.
> Interestingly enough the same SSL error seems to occur when I connect via
> named pipes instead of TCP/IP. I was not aware that SSL could be used
over
> anything besides TCP/IP. I would really just like to get the server
running.
> I have no need for this SSL business.

--
Posted via CNET Help.com
http://www.help.com/