Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates
cancel
Showing results for 
Search instead for 
Did you mean: 
seanmNL1
Contributor II
Contributor II

OLE DB not supporting TLS1.2 preventing Qlikview comms with SQL server

Hello

I have updated OLE DB on our SQL Server to allow QlikView communicate via TLS 1.2 

I believe to complete this I need to change the OLE DB connection string on the ClikView server to something like this:

Provider=MSOLEDBSQL

My question is where do I make this change? Do i make it on the Qlikview server or on the SQL Server? If it ios on the QlikView server then where on it do I make the change?

Labels (2)
4 Replies
Maria_Halley
Support
Support

If the connection string has changed than you would have to change it in the script.

But in general to make TLS1.2 work you don't have to do anything on the QlikView side. 

Maria 

seanmNL1
Contributor II
Contributor II
Author

Hello Maria

Do I have to make the change within each document?

I opened one of the document and then got the option to "Edit Script"

Then under the Data tab I have OLE DB listed and can hit the "Connect" button which brings up various Providers.

Which one of these should I choose?

Attached is a screenshot of my options

seanmNL1
Contributor II
Contributor II
Author

Could someone come back to me on this please?

I did choose the "MS OLE DB Provider for SQL Server" and entered config details.

The "Test Connection" worked fine.

A connection script seemed to have been created. I saved the document but then the document/task failed to reload.

Please How can we resolve this please?

Lucas_Gatling
Support
Support

@seanmNL1  Can you share the document log of the QVW that is failing to reload? 

If the issue is solved please mark the answer with Accept as Solution.