Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved TLS 1.2 and ODBC

  1. Issue
0
Votes
Undo
  1. Thomas Rolseth
    Thomas Rolseth
  2. PowerBuilder
  3. Thursday, 17 December 2020 18:47 PM UTC

We have a PB 2019 R2 application connecting to a SQL Server 2016 database using the old SQL Server driver (sqlsrv32.dll).  The OS is Windows 10 Enterprise.  The connection is scripted as follows:

 

SQLCA.DBMS = lsODBCTrace + "ODBC"
SQLCA.LogId = ls_ap_user
SQLCA.LogPass = ls_Password
SQLCA.AutoCommit = true
SQLCA.Lock = lsODBCLock

lsdbParm = "CONNECTSTRING='Driver={SQL Server};Server=" + ls_sqlca_servername + ";Database=" + ls_sqlca_database + ";UID=" + ls_ap_user + ";PWD=" + ls_Password + "',DisableBind=1,DelimitIdentifier='No',CallEscape='No'" + ",CursorScroll='Static',TrimSpaces='YES'"

SQLCA.DBParm = lsdbParm
Connect;

 

This code works great but when TLS 1.0 is disabled in the registry this connection fails (see attached error).  We thought we might try using the ODBC 13 driver and so changed the above to this:

 

SQLCA.DBMS = lsODBCTrace + "ODBC"
SQLCA.LogId = ls_ap_user
SQLCA.LogPass = ls_Password
SQLCA.AutoCommit = true
SQLCA.Lock = lsODBCLock

lsdbParm = "CONNECTSTRING='Driver={ODBC Driver 13 for SQL Server};Server=" + ls_sqlca_servername + ";Database=" + ls_sqlca_database + ";UID=" + ls_ap_user + ";PWD=" + ls_Password + "',DisableBind=1,DelimitIdentifier='No',CallEscape='No'" + ",CursorScroll='Static',TrimSpaces='YES'"

SQLCA.DBParm = lsdbParm
Connect;

 

Unfortunately that doesn't work.  We are not using DSN profiles or a trusted connection.  Given that, has anyone used the ODBC 13 driver in a PB app with SQL Server and if so, what was your connection string assigned to the DBParm value?  Or is our only option to wait for the R3 release?

Thanks, Tom

 

 

Attachments (1)
sql_server_error.png sql_server_error.png
  1. ODBC
  2. PowerBuilder
  3. SQL Server
  4. Windows OS
What is required to install Appeon PowerBuilder Ru...
Alternate Characters in dynamic menu
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 17 December 2020 19:18 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Thomas;

  TLS 1.2 support is coming for SS in PB 2019 R3 release - for both SNC and the new DB driver  ... https://docs.appeon.com/pb2019r3/whats_new/MS_SQL_Server_enhancements.html

  Also, this Microsoft article might be helpful for utilizing TLS 1.2 from the SS perspective ...

https://support.microsoft.com/en-us/help/3135244/kb3135244-tls-1-2-support-for-microsoft-sql-server

HTH

Regards ... Chris

Comment
There are no comments made yet.
Responses (2)
Thomas Rolseth
Thomas Rolseth Accepted Answer Pending Moderation
  1. Thursday, 17 December 2020 18:47 PM UTC
  2. PowerBuilder
  3. # 1

Also, the application is 32-bit

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 17 December 2020 19:09 PM UTC
Yup, or if using PB 2019 R3 the new driver MSOLEDBSQL.
  1. Helpful
Thomas Rolseth
  1. Thomas Rolseth
  2. Thursday, 17 December 2020 21:47 PM UTC
To confirm, using ODBC Driver 13 for SQL Server (msodbcsql13.dll) will not work with TLS 1.2?
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 18 December 2020 00:08 AM UTC
I'm not sure... almost everybody that uses SQL Server goes with native interface, and I know for sure that TLS 1.2 does work for native interface.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.