Qlik Community

Ask a Question

Knowledge Base

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
Live chat with experts, bring your API Integration questions. June 15th, 10 AM ET. REGISTER TODAY

App Reload Fail With "Error: QlikView Connector is not responding" Or "Connector is not responding".

Sonja_Bauernfeind
Digital Support
Digital Support

App Reload Fail With "Error: QlikView Connector is not responding" Or "Connector is not responding".

Scenario:

  • Qlik Sense has restricted, slow or no internet connection. 
  • App reload fails with error message "QlikView Connector is not responding" or "Connector is not responding".
  • Sheets are slow to open.
  • ErrorCode.11041 occurs when opening up an App
  • ErrorCode.11043 occurs when creating a Database connection in the data load editor.

 

Environment:

QlikView , all versions

 

Cause:


Qlik connectors are cryptographically signed for authenticity verification. The .NET framework verification procedure used for this signing includes checking OCSP and Certificate Revocation List information, which are fetched from a online resource if the system doesn't have a cached local copy. These requests will timeout due to lack of access to online resource in environments with restricted, slow or no internet connection. Due to authenticity check failure the connector will not run, and the app reload fails. 

Qlik R&D is evaluating options to mitigate the effect of restricted, slow or no internet connection for future releases of Qlik Sense.

 

Resolution:


This issue can be resolved by disabling the online dependency for .NET framework based authenticity verification. 

There are two (2) ways of accomplishing this, either by modifying the configuration file for each connector or by changing the .Net Framework's machine.config file on a global level which applies for all connectors.

Option 1: Editing the Connector configuration file:Stop all Qlik Sense services on all nodes

  1. Open the config file in the connector folder in C:\Program Files\Common Files\Qlik\Custom Data\ 
    for instance C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe.config
  2. Add the following values before the closing </configuration> tag: 
    <runtime> 
        <generatePublisherEvidence enabled="false"/> 
    </runtime>
  3. Repeat steps 2 and 3 for all nodes and all .config files
    • C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe.config
    • C:\Program Files\Common Files\Qlik\Custom Data\QvDataMarketConnector\QvDataMarketConnector.exe.config
    • C:\Program Files\Common Files\Qlik\Custom Data\QvSalesforceConnector\QvSalesforceConnector.exe.config
    • C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector\QvRestConnector.exe.config


Option 2:  Editing the .Net Framework's machine.config file

  1. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
     
    a) If there is a <runtime/> tag, change it to
    <runtime>
        <generatePublisherEvidence enabled="false"/>
    </runtime>

     
    b) If there is other stuff in the <runtime> section, then change it to look like this:
     
    <runtime>
      <some other="stuff">
        <...>
      <generatePublisherEvidence enabled="false"/>
    </runtime>
  2. Save machine.config
  3. Repeat on all nodes (if applicable)

NOTE1: Changes to machine.config affects all software using the .NET framework feature. 
NOTE2: 3rd party connectors might be compiled for 32-bit platforms. In such case repeat steps above for the 32-bit version of the machine.config file; Path C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config

 

Internal Investigation IDs:

  • QLIK-66335
Labels (2)
Version history
Revision #:
2 of 2
Last update:
3 weeks ago
Updated by:
 
Contributors