Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Qlik sense encrypted connection to SQL db

Hi

I am trying to use encrypted database connections to a SQL Server db.

We have installed a certificate in the SQL Server db and have the Root CA certificate also on the client from where i am running qlik sense.

when i configure qlik sense to 'trust the server certificate' i can make a successful connection to the database.

but when i un-check 'Trust Server Certificate', which should enforce a check on the client side that the certificate on the db site is valid and trusted, i get the following error:

Error message:

Please check the values for Username, Password, Host and other properties.

Description: Client unable to establish connection

Details:

ERROR[08001][Simba]Problem establishing connection to server

Anybody encountered the same issue and can help with the resolution?

Thanks for any help

  Klaus

4 Replies
leonardo_marmir
Partner - Contributor
Partner - Contributor

I encountered the same issue, but i can't help you.

I'm sorry

Anonymous
Not applicable
Author

Hi Klaus,

did you tried to create a connection with the original Microsoft ODBC driver?

Cheers!

Christian

Anonymous
Not applicable
Author

Yes, creating an ODBC connection with the sql native client and encryption works.

I would have loved to use the MS SQL facade that Qliksense provides but somewhere in the 'translation' must be an issue when using certificates. i am trying again now and get an error message with the same number but a slightly different message.

ERROR[08001][Simba]Failed verifying server credentials

Maybe the qlik team can have a look and provide a more descriptive error message that would help to resolve the issue.

Cant copy and paste from the error popup either ... just not my day today.

CodeKazuko
Contributor III
Contributor III

Can use default snipping tool for the error if using windows.