Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
DesmoArka
Partner - Contributor III
Partner - Contributor III

Maybe APRIL 2020 Oracle driver connector bug?

Hi guys,

I have uptade old release to APRIL 2020.

I have an application with an oracle connection create with integrated connection wizard in sense.

After update sense can't load odbc driver to fetch data. 

This is the error in C:\ProgramData\Qlik\Custom Data\QvOdbcConnectorPackage\Log\QvOdbcConnectorPackage.log:

oracle TestConnect was not successful: message='Error message: Please check the values for Username‚ Password‚ Host and other properties. Description: Specified driver could not be loaded', detailMessage='ERROR [IM003] Specified driver could not be loaded due to system error 126: The specified module could not be found. (Qlik-oracle, C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\oracle\lib\OracleODBC_sb64.dll).'. 

The path exists and OracleODBC_sb64.dll too.

My actual work around is creating connection in administrative tools in windows and than add that odbc connection in sense.

does somebody else have this problem?

Thanks

Labels (1)
9 Replies
Albert_Tjahyono
Contributor II
Contributor II

Anyone had the same case? Is there any solution for this?

charlie_firemind
Partner - Contributor III
Partner - Contributor III

Sadly the answer is yes.

Have logged a ticket with Support on the 6th, awaiting a response.

Thanks,

Charlie

Anonymous
Not applicable

This is being investigate as a bug.

The current workaround is to use the previous version of the ODBC Connector Package shipped with QS February 2020 or earlier.

charlie_firemind
Partner - Contributor III
Partner - Contributor III

Thank you Tomasz for the update.

Albert_Tjahyono
Contributor II
Contributor II

How did we install the ODBC Connector Package from QS Februari 2020?
From the download link, there is only ODBC Connector v6.16.

Can we use this version for the workaround?

charlie_firemind
Partner - Contributor III
Partner - Contributor III

The latest Simba Oracle ODBC driver supports OCI19. OCI19 has dependency on Microsoft Visual C++ 2017. The R&D team are working on addressing the issue.

In the meantime the workaround is the following:

It is necessary to copy the library vcruntime140.dll in Oracle lib folder:

Qlik Sense Desktop: C:\Users\<User>\AppData\Local\Programs\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\oracle\lib

Qlik Sense Server: C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\oracle\lib

or 

Download and install the Microsoft Visual C++ Redistributable Packages available at https://aka.ms/vs/16/release/vc_redist.x64.exe

Anonymous
Not applicable

@Albert_Tjahyono  @charlie_firemind 

You can just swap the current version of the ODBC Connector Package with the previous one - 6.16 is fine. Also the workaround from @charlie_firemind works.

uwqliker
Contributor
Contributor

We got the exact same error when we tried to upgrade from Nov 2019 to April 2020. So we instead tried the February 2020 release thinking that would be more stable and were able to get our install to work in our dev environment after some issues and tweaking.

We tried to recreate the Feb 2020 install on our Test environment, but now we're getting that same 126 error on Oracle connections and we can't get it to work.

rusanov_eduard
Contributor II
Contributor II

Thank you @charlie_firemind 

Download and install the Microsoft Visual C++ Redistributable Packages available at https://aka.ms/vs/16/release/vc_redist.x64.exe

We have the same release as yours, Qlik Sense Feb 2020. Installed C++ libs on all nodes, restarted all services on all nodes.

Another option, more stable, create an odbc connector for Oracle.
It turned out to be more stable after several Qlik Sense updates.