• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • TLS 1.2 when using SNC SQL Native Client(OLE DB) as DBMS for transaction

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

Resolved TLS 1.2 when using SNC SQL Native Client(OLE DB) as DBMS for transaction

  1. How-to
0
Votes
Undo
  1. Lawrence Anderson
    Lawrence Anderson
  2. PowerBuilder
  3. Tuesday, 18 August 2020 19:45 PM UTC

I'm running PowerBuilder 2017 R3. We're looking to switch our database to require TLS 1.2. We're connection to a SQL Server with a DBMS of SNC SQL Native Client(OLE DB) and provider of SQLNCLI11.  Using a transaction I am setting the parameters for the transaction, connecting to the database, and writing to a table.

It is working in development but not on certain computers in production. User receives an error indicating "TCP Provider: An existing connection was forcibly close by the remote host". We've set up a new computer and ran through the process while impersonating a user experience issues, and have been successful. So it likely with their setup, I'm just not sure how exactly.

dw1.Object.DataWindow.Data.XML
Powerbuilder & OLE & Word
Accepted Answer
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 19 August 2020 01:26 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Lawrence,

This issue is usually caused by two reasons. Your problem is more likely due to the second one.

1. A wrong provider is specified in DBParm. If you have not specified the Provider in SQLCA.DBParm, it will use SQLNCLI (for SQL Server 2005) which does not support TLS 1.2. The correct one is like below.

SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"
SQLCA.DBParm ="Database='test',Provider='SQLNCLI11',Encrypt=1,TrustServerCertificate=1"


2 The SQL Server Native Client on the machine does not support TLS 1.2, even SQL Server Native Client 11.0 requires to be upgraded to the correct version, please go to the link below to update SQL Native Client 11.0.
https://www.microsoft.com/en-us/download/details.aspx?id=50402

You can refer to the article below for more details.
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server


Regards,
ZhaoKai

Comment
Lawrence Anderson
  1. Lawrence Anderson
  2. Friday, 21 August 2020 19:58 PM UTC
Thank you, it was the second one. I had suspected it was a driver, but missed the TLS 1.2 hotfix.
  1. Helpful
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Monday, 24 August 2020 00:03 AM UTC
Glad to hear that.
  1. Helpful
There are no comments made yet.
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 August 2020 19:52 PM UTC
  2. PowerBuilder
  3. # 1

Hi Lawrence;

   When this issue happens .. is there any corresponding information in the SS DB Log as the possible issue?

Regards  ... Chris

Comment
There are no comments made yet.
Lawrence Anderson
Lawrence Anderson Accepted Answer Pending Moderation
  1. Tuesday, 18 August 2020 20:08 PM UTC
  2. PowerBuilder
  3. # 2

Under management for the overall server, it does not appear to show an event.

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 18 August 2020 20:28 PM UTC
  2. PowerBuilder
  3. # 3

if you google your question you will find:

https://support.microsoft.com/en-us/help/4557473/errors-when-applications-try-to-connect-to-sql-server-in-windows

Comment
Lawrence Anderson
  1. Lawrence Anderson
  2. Tuesday, 18 August 2020 21:17 PM UTC
User computer is Windows 10 1909 and Server 2019 14.0.2027 so they both have the leading zero fixes for TLS_DHE.
  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.