• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Windows could not connect to SQL Server after tls upgrade to tls 1.2

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

Resolved Windows could not connect to SQL Server after tls upgrade to tls 1.2

  1. Issue
0
Votes
Undo
  1. Minogue Susan
    Minogue Susan
  2. PowerBuilder
  3. Wednesday, 24 April 2024 12:26 PM UTC

We have windows based application developed on PowerBuilder 2017 and which connects to SQL server 2014. Recently, server protocol upgraded to tls 1.2. From then, application can not connect to database server and it throws SSL hand shake failed error. Please advise. 

  1. PowerBuilder
  2. TLS/SSL
  3. Windows OS
import pdf files from my computer to dw report
Passing pointers with external function in 64bits
Responses (5)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 24 April 2024 13:44 PM UTC
  2. PowerBuilder
  3. # 1

I believe TLS 1.2 for SQL Server was not supported in PowerBuilder until version 2019 R3.

    https://docs.appeon.com/pb/whats_new/MS_SQL_Server_enhancements.html

Best regards, John

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 24 April 2024 13:59 PM UTC
  2. PowerBuilder
  3. # 2

SQL Server 2014 support end date was Jul 9, 2019. PowerBuilder 2017 is also out of support. You should upgrade both.

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 24 April 2024 18:25 PM UTC
  2. PowerBuilder
  3. # 3

As Roland and John said, upgrade PowerBuilder to PB 2022 R3 and use the MSOLEDBSQL driver if you want to use TLS 1.2.

Comment
There are no comments made yet.
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Wednesday, 24 April 2024 21:57 PM UTC
  2. PowerBuilder
  3. # 4

Hi Susan,

if you use ODBC, you will be fine if you install a newer ODBC Driver for SQL Server that supports TLS 1.2.

Eventually you have to set TrustServerCertificate in the ConnectionString, depending on the "quality" of your certificates.

hth

Arnd

Comment
There are no comments made yet.
Minogue Susan
Minogue Susan Accepted Answer Pending Moderation
  1. Thursday, 11 July 2024 12:28 PM UTC
  2. PowerBuilder
  3. # 5

We have upgraded Application to PB2022 and updated connection string to OLEDB driver. but it throws DB code 18456. We are able to connect SQL server from other .net app and SSMS so we are good with connectivity from ID but got an error from PowerBuilder app.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 11 July 2024 15:38 PM UTC
Hi Susan;

The current Microsoft DB Client driver for SS is now ""MSOLEDBSQL". MS recommends that you start using this DB Client vs older SS DB drivers going forward. PB 2022 supports this latest MS SS DB Client via the setting ... SQLCA.DBMS = "MSO" // short for MSOLEDBSQL

HTH

regards .. Chris
  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.