SQL Server Developer Center > SQL Server Forums > SQL Server Data Access > SSL Security Error with app using MS SQL 2005
Ask a questionAsk a question
 

Proposed AnswerSSL Security Error with app using MS SQL 2005

  • Wednesday, November 04, 2009 12:05 PMRafalDz Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,
    I'm a using Windows 7 RC1 and I have a strange problem. I've installed an application using odbc driver to connect to MS SQL 2005. This application isn't brand new, however it has worked perfectly... for two days. Now, when I try to log into the application, I keep getting "SSL Security Error". Problem is that my MS SQL Server doesn't use any connection encryption. I also tried to use cliconfg.exe to check wheter my sql client is trying to communicate with sql server via encrypted channel. Well configuration was ok.
    For a moment I was thinking that maybe some updates caused this problem but I've reinstalled windows with all updates and programs I'd installed previously. Again, my application has worked for two days. Than it stoped again with the same error message.
    What's more. I've setup virtual pc with another, fresh copy of windows with all apps and updates and it's been working for two weeks now. I've made a connection trace for both windows copies. Here are the results:

    1) On windows with error:
    "[Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error"

    2) On windows without a problem:
    "[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to  master"

    I've found that difference is in entries about odbc driver (DBNETLIB vs SQL Server). Can that be a problem? If so how to correct it? As I said it doesn't seem to be a problem of an application Im trying to make to run, cause it worked on host computer, and it's working on virtual pc.

    Help! :)

    Best Regards

    Rafał
    • Edited byRafalDz Wednesday, November 04, 2009 3:02 PMtypos
    •  

All Replies

  • Friday, November 06, 2009 5:59 PMDan BenediktsonMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    Can you try configuring the application to use a different ODBC driver? Since this is SQL Server 2005, the preferred ODBC driver is the "SQL Native Client" driver, but the "SQL Server" driver should work just as well. DBNETLIB is very old and depending on server configuration may run into problems.


    This post is provided 'as is' and confers no express or implied warranties or rights.
  • Monday, November 09, 2009 11:36 AMRafalDz Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Well. There is no possibility to configure this application to use another library (not in app itself, nor ini files, nor registry). I tried to create an alias but tbh Im not sure if I'm using proper parameters as I'm getting the same ssl security error or "no sql server found".
    Still I wonder what could possibly happen to my working w7 copy that it doesn't work while on another, testing copy it works perfectly :/