The Qlik Sense Data Manager and Data Connection does not load when opening the Data Load Editor or Add Data Wizard. The Qlik Sense hub does not load a data connection or takes too long to load it.
This issue happens predominantly in Deployments within Environments with restricted Internet access. The workaround is to remove the Custom Data Connectors from the installation folder.
Other symptoms might include:
ErrorCode.11041 occurs when opening up an App
ErrorCode.11043occurs when creating a Database connection in the data load editor.
After fresh installation or upgrade the User navigates to the Data Load Editor or Add and sees the following:
And the Data Connection List is empty and the loading wheel is spinning indefinitely:
In Add Data Wizard following can be observed:
In most cases depending on the environment the Data Connections will eventually load after 10 to 30 minutes of waiting. However this not an ideal solution as the connections have to be loaded every time when the Data Load Editor or Add Data Wizard are accessed.
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.
Alternatively, using a third-party tool such as Fiddler or inbuilt browser debug tools, identify the addresses used and add them to allow lists on firewalls/proxies otherwise blocking internet traffic.
Temporarily move the following files outside of Program Files:
OvOdbcConnectorPacakage and OvDataMarketConnector
Files can be found in: C:\Program Files\Common Files\Qlik\Custom Data
In a multi node environment please do it for all the nodes. You can as well try removing only the OvOdbcConnectorPacakage as the OvDataMarketConnector does not always fail.
Note that when moving the files, you will not be able to use the Data Market Connector or the ODBC Pacakage.