Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Rehan
Creator III
Creator III

Unencrypted Connection String

We are using QV 12.3 server. Our Database team sent us an email that apparently there is an unencrypted account being used by QvConnect64.EXE and the username mentioned is teh username used to extract data from the database. We have a lot of QVD generator. What is the best way to located that particular generator using the unencrypted account other than  going through every single generator.

1 Solution

Accepted Solutions
Miguel_Angel_Baeyens

QlikView relies on the operating system DSNs or product drivers to extract data, even when the Qlik Connector suite is installed (i.e.: Qlik does not connect direcly to any data source other than CSV, XLS and QVD files).

The definition of the string used to connect will be most likely in ODBCAD32.exe, which can be found on

  • C:\Windows\System32\odbcad32.exe (for 64 bit connections)
  • C:\Windows\SysWoW64\odbcad32.exe (for 32 bit connections)

Check there and see which one is set as unencrypted.

Worth mentioning: the drivers you use to connect to that source might not allow encryption. 

Using the QlikView Governance Dashboard can help you finding which connection string has certain properties under the Lineage sheet, but the change will have to be done using the driver itself or via the tools mentioned above.

View solution in original post

1 Reply
Miguel_Angel_Baeyens

QlikView relies on the operating system DSNs or product drivers to extract data, even when the Qlik Connector suite is installed (i.e.: Qlik does not connect direcly to any data source other than CSV, XLS and QVD files).

The definition of the string used to connect will be most likely in ODBCAD32.exe, which can be found on

  • C:\Windows\System32\odbcad32.exe (for 64 bit connections)
  • C:\Windows\SysWoW64\odbcad32.exe (for 32 bit connections)

Check there and see which one is set as unencrypted.

Worth mentioning: the drivers you use to connect to that source might not allow encryption. 

Using the QlikView Governance Dashboard can help you finding which connection string has certain properties under the Lineage sheet, but the change will have to be done using the driver itself or via the tools mentioned above.