Results 1 to 7 of 7
  1. #1
    Join Date
    Aug 2012
    Posts
    8

    Unanswered: SSL Security Error

    We have a VB.2010 desktop app that access MS SQL databases via ADO. Has been working for years.

    Used it with a new customer running Windows Server 2012, SQL Server 2012 and we cannot connect to the DB. Get SSL Security Error.

    App uses a DSNless connection via Connection String.
    DRIVER={SQL Server};DESC=;DataBase=dbname;SERVER=n.n.n.n;UID=. ..;PASSWORD=...;SSLMode=Required
    Tried with the SSLMode and without.

    We can connect via the SQL Server Mgmt Admin app.

    Always get the SSL Security error.

    Can you tell me what is wrong?

    Thanks

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,862
    Provided Answers: 17
    The version of the driver could have changed between machines. Confirm that by looking at the drivers tab in ODBCAD32. SSLMode does not appear to be an option for the SQL Server driver, though. See https://msdn.microsoft.com/en-us/library/ms130822.aspx.

    If you are trying to encrypt the traffic between the client and the SQL Server, you may need to do that in the SQL Server Configuration Manager.

  3. #3
    Join Date
    Aug 2012
    Posts
    8
    It fails from my machine both old and new so I don't think it is the driver.

    I was able to get it to work by changing the ODBC methods from ADO to SQLConnection/SQLDataReader. The connection string is different but fundamentally the same info.

    So what is different between ADO and SQLConnection?

  4. #4
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,445
    Provided Answers: 12
    SSLMode doesn't look like the right connection string parameter.

    Check the list here: https://www.connectionstrings.com/al...ring-keywords/

    Try:
    Code:
    Encrypt=True;
    George
    Home | Blog

  5. #5
    Join Date
    Aug 2012
    Posts
    8
    I tried with and without SSLmode. The connection string I started with did not have SSLMode and did not work for this DB but it did work for all other MS SQL DB in the past.

    So why is SQLConnection working but not ADO with this DB.

  6. #6
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,862
    Provided Answers: 17
    SQLConnection is ADO.NET, so it uses SQLClient rather than OLEDB, or (shudder) MSDASQL.

  7. #7
    Join Date
    Aug 2012
    Posts
    8
    That doesn't explain why the old method did not work with this one database.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •