Qlik Community

Ask a Question

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Talk to Experts Tuesday: Live chat Aug. 24th 10 AM ET: Bring your Qlik Gold Client questions REGISTER TODAY

QvConnect64.exe and QvConnect32.exe are not digitally signed

Sonja_Bauernfeind
Digital Support
Digital Support

QvConnect64.exe and QvConnect32.exe are not digitally signed

QvConnect64.exe and QvConnect32.exe are not digitally signed and cannot launch in restricted environments only allowing digitally signed software. 

The EXE created in the APPDATA\Roaming directory is not digitally signed. 


Environments:

QlikView Desktop 12.20 any previous versions
QlikView Desktop 12.40 



Resolution:


This is working as intended. However, a feature was introduced that allows for the configuration of a different temporary path.

Open the settings.ini file of the QlikView Desktop client. 

  • This is located in C:\Users\USER\AppData\Roaming\QlikTech\QlikView
  • Add the following line:
    QVConnectFolderTmpPath=C:\YourFolder\
  • The line should be added between the [Settings 7] section and the [Authentication] section.
  • Save the file.

After this, the qvconnect32.exe or qvconnect64.exe will be copied to the specified folder.

This functionality is available beginning with:

QlikView November 2017 (12.20 SR 7)
QlikView November 2018 (12.30 IR)
QlikView April 2019 (12.40 IR)

 

Cause:


Each time that QlikView is executed it overwrites the "QvConnect" files in the folder C:\Users\ <USER>\AppData\Local\Temp\QVConnect\ 
QlikView use the QvConnect files located in the folder C:\Users\ <USER>\AppData\Local\Temp\QVConnect\to configure the db connection.
This .exe is not signed. 
 

Labels (2)
Version history
Revision #:
2 of 2
Last update:
‎2020-09-01 04:00 AM
Updated by:
 
Contributors