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.
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
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
Add the following values before the closing </configuration> tag: <runtime> <generatePublisherEvidence enabled="false"/> </runtime>
Repeat steps 2 and 3 for all nodes and all .config files
NOTE1: Changes to machine.configaffects 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