When creating OLE DB or ODBC connection, QlikView Desktop shows error "Failed to connect to Qlikview Connector"
or "Failed to unbundle QVConnect"
(the processes handling 32 and 64-bit OLE DB/ ODBC connections in QlikView)
are bundled into C:\Program Files\QlikView\Qv.exe
. On the first time the script editor is opened, these QvConnect files will be extracted into C:\Users\<user>\AppData\Local\Temp\QVConnect\<QlikView version>\
. This implementation ensures that QvConnect always match the current Qv.exe
- If current user has no access to this path, QlikView cannot extract QvConnect files and shows error "Failed to unbundle QVConnect"
- If there is a security protection (such as a group policy or antivirus) that block file execution from this path, QlikView is unable to run these exe files and shows error "Failed to connect to Qlikview Connector"
- QvConnect64.exe and QvConnect32.exe are not digitally signed
Currently this path is hardcoded, so it is not possible to configure QlikView to pick up another path. QV-14723
From QlikViewDesktop 12.30 IR and up it is possible to change the default path.
The path can be changed in the settings.ini file to a path different from Temp, the connectors copy will be carried out onto that specified folder and not in Temp
The settings.ini file can be found here: C:\Users\<User>\AppData\Roaming\QlikTech\QlikView
Add a new line under [Settings 7]
Make sure the current user running QlikView Desktop has full access to the path C:\Users\<user>\AppData\Local\Temp\QVConnect\<QlikView version>\2.
and QvConnect64.EXE already exist in this path, try to run these exe files to see if there is any error message similar to the followings:
If a similar error message shows up, QlikView is unable to lauch QvConnect due to a group policy restriction. Request system or domain administrator to add an exception to this group policy so that QvConnect32.EXE
and QvConnect64.EXE can be executed from this path.