

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cant Connect to Sql Server
Hi guys,
bit of a loss here - My IT dept have moved my DW to a new server (the data warehouse was sitting on an old 2008 box). Since the DW has moved to a new server, none of my Sql conn connections work (QlikView & QlikSense). I assumed it was a firewall permissions issue, but it appears not the case. I must add that i have no access to my servers, instals etc as our IT dont allow it, therefore my knowledge is limited!
error message from QS is: "The following error occurred:
Connector connect error: IDataInitialize::GetDataSource. HRESULT = 80004005. ErrorSource: Microsoft OLE DB Provider for SQL Server, ErrorMsg: [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.
The error occurred here:
OLEDB CONNECT TO ***
"
from our IT guy: "
[Yesterday 15:57]
I think (but don't know for sure) that it's because the new boxes are on a newer operating system with older, less secure protocols disabled. I.E. TLS 1.0 and TLS 1.1 are disabled
[Yesterday 15:57]
Operating system is windows server 2016.
[Yesterday 15:58]
SQL server is 2016 also (but the version of SQL server hasn't changed)"
something to do with I.E. TLS?
cheers
Accepted Solutions

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
If you are using the natived SQL that is supplied by the OS, then do not support this. You will need to download the updated drivers. See below articles.
https://community.qlik.com/t5/Official-Support-Articles/OLEDB-Connection-not-working-with-TLS-1-2/ta...
https://community.qlik.com/t5/Official-Support-Articles/OLEDB-Connection-not-working-with-TLS-1-2/ta...
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Both QlikSense and QlikView support TLS.
See
https://community.qlik.com/t5/Knowledge/Supported-TLS-and-SSL-Protocols-and-Ciphers/ta-p/1710345
Microsoft OLE DB Driver for SQL Server has supported TLS1.2 since 2018.
So that should not be the problem.
Did you update the connection strings?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please share your resolution

.png)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
If you are using the natived SQL that is supplied by the OS, then do not support this. You will need to download the updated drivers. See below articles.
https://community.qlik.com/t5/Official-Support-Articles/OLEDB-Connection-not-working-with-TLS-1-2/ta...
https://community.qlik.com/t5/Official-Support-Articles/OLEDB-Connection-not-working-with-TLS-1-2/ta...
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I started my first role as a BI at a mid-size company a few months ago. The company is Fintech/banking focused and still has a start-up mentality in terms of how things are done (fast and no planning). Our BI team is divided according to the business units we do work for. Our department is 6 people overall, 4 of us very juniors
When I joined, they already had a SQL server DW that feeds into Qlik sense for the devsion I work for, while the other division feeds directly from (many) source dbs into qlik view. Our head of department works exclusively for the second division.
The head of department keeps saying how a SQL DW is a waste of time, we shouldn't be spending time creating transforms and staging data to bring into our Qlik sense models. We should just be bringing in raw data directly into our front end like his division does.
I'm a bit frustrated with this because compared to SQL, qlik has really few online resources to refer to when I get stuck trying to create some view ki/aggregate and stage data for analysis. We are constantly being told we're not working fast enough and should just do the quickest solution possible rather than create something sustainable.
I wanted to ask if this is common? How many companies with banking volume of transactional data and half a dozen products use qlik as a DW?
