SSL Security Error

 >-----Original Message-----
 >Check the following registry key on the client machine.
 >
 >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\S
uperSocketNetLib
 >If the Encrypt value is set to 1, then the client is
requesting SSL.
 >
 >Also, your application may be requesting it thru a
connection string option
 >or the ODBC DSN could also be set to Enable encryption.
 >
 >You could also make a network trace from the client
machine to verify if
 >the Server does have a certificate installed. This
information is sent
 >back to the client during the preloginhandshake.
 >
 >
 >Thanks,
 >
 >Kevin McDonnell
 >Microsoft Corporation
 >
 >This posting is provided AS IS with no warranties, and
confers no rights.
 >
 >
Thanks for your reply Kevin.

I have checked SuperSocketNetLib on my client workstation
and it is set to 0, there is no encryption set in the ODBC
DSN.

So, am I now looking for the same setting
(SuperSocketNetLib) in the registry of the server? And if
the server had this setting, why would it be demanding SSL
encryption from some clients but not others?

There is no way I can get access to the server in my
particular corporate environment. So I will need to
document the whys and wherefores in some detail and submit
a request to change this setting.

More detail will be most welcome.

regards,
Vossaka
 >> Stay informed about: SSL Security Error 

The serverside key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNet
Lib

Encrypt:

If your client is using MDAC 2.7, then you could be running into the
following issue;

322144 FIX: SECDoClientHandShake Cannot Connect to SQL Server
http://support.microsoft.com/?id=322144

I would suggest making a network trace from the client machine and
reviewing it with your network team. Also,
check to see what account the SQL server is running with.


Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.
 >> Stay informed about: SSL Security Error 

Yes McDonnel,

We also receive the same error. But the issue is a bit different. Th
environment had changed from Windows 2000 to Windows 2003. The SQL D
Server machine also got changed from Windows 2000 to Windows 2003.

Now we got an application which actually imports data into the DBServe
database.

When the application is manually invoked and run after filling in th
text boxes with necessary information import was successful.

But when the same application is invoked using a batch script file, th
application is started and all the parameters are filled in the tex
boxes of the application. But import doesnt happen. We get two types o
error at different times.

First one is
-----------
2006\06\06 11:56:09 General SQL error.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpe
(SECDoClientHandshake()).
Alias: PRODUS

Second one is
-------------
2006\06\26 06:52:56 Read failure.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrit
(SECEncryptData()).
Alias: PRODUS


From your discussion I understand some secure connection request i
trying to establish from client. But if that is the case why should i
work when manually invoked and why shouldnt it work when invoked with
batch.



Thanks in Advance
Suresh Kannan from Indi

--
sureindi
-----------------------------------------------------------------------
sureindia's Profile: http://www.dbtalk.net/m47
View this thread: http://www.dbtalk.net/t15369
 >> Stay informed about: SSL Security Error