Skip to main content
Solved

How to fix Provider error `(-2147467259) Encryption not supported on the client.' Failed to open reader on FME 2019.2?

  • April 14, 2020
  • 1 reply
  • 907 views
kpyke5
Contributor
Forum|alt.badge.img+5

Hi FME Community,

I am moving some FME workbenches from a 2012 microsoft server to a 2019 microsoft server and am finding some issues with running a few of them. The person who originally set up the workbench I am trying to get to run is no longer with the company and I arrived after they left.

I am trying to read in table features on a MSSQL_ADO reader and keep running into this error:

 

Provider error `(-2147467259) Encryption not supported on the client.'

 

Failed to open reader

 

I am thinking it has to do with the new server or some configuration that needs to be done somewhere.

 

I have found a few leads

Thanks!

Best answer by kpyke5

Hi, The IT department got back to me quicker than I thought and I figured I would post the solution here in case anyone else runs into this problem. You need to update the sql native client. This is what my IT department said to me specifically:

 

"this wasn't specific for FME but it was the same error.

Solution / Workaround

 

If you use TLS 1.1 or 1.2 as default secure protocols instead of TLS 1.0 and use older release of SQL Server Native Client 2012 then this issue can occur. This will result in unusable vault as M-Files services won't be able to communicate with MS SQL server and will result in failing to bring the vault online.

 

 

You must update your SQL Server Native Client to build 11.3.6538.0 or higher for enabling support for TLS 1.1 and 1.2. Older versions don't support TLS 1.1 or TLS 1.2. "

 

IT updated us to 11.4 and FME could use the readers again.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

kpyke5
Contributor
Forum|alt.badge.img+5
  • kpyke5Contributor
  • Author
  • Contributor
  • Best Answer
  • April 14, 2020

Hi, The IT department got back to me quicker than I thought and I figured I would post the solution here in case anyone else runs into this problem. You need to update the sql native client. This is what my IT department said to me specifically:

 

"this wasn't specific for FME but it was the same error.

Solution / Workaround

 

If you use TLS 1.1 or 1.2 as default secure protocols instead of TLS 1.0 and use older release of SQL Server Native Client 2012 then this issue can occur. This will result in unusable vault as M-Files services won't be able to communicate with MS SQL server and will result in failing to bring the vault online.

 

 

You must update your SQL Server Native Client to build 11.3.6538.0 or higher for enabling support for TLS 1.1 and 1.2. Older versions don't support TLS 1.1 or TLS 1.2. "

 

IT updated us to 11.4 and FME could use the readers again.

Community Stats

32,120
Posts
121,954
Replies
39,772
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.