An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet
Changes must be made to any Qlik server that will not be provided with internet access.
This is mainly due to the Qlik DataMarket reaching out to the internet although it may not even be used. Undoing or not agreeing to the Qlik DataMarket Terms of Service does not fully disable certain Qlik DataMarket functionalities.
NOTE: Qlik DataMarket is being discontinued, and Qlik Sense Enterprise on Windows versions February 2021 and newer will no longer have it included. For updated information see Qlik DataMarket will be retired
For servers not connected to the internet, they may be prompted with a pop-up error when browsing in the Hub or in the Data Load Editor with the following errors:
The Hub has continuous bubbles while loading forever
The Hub is stock on the initial loading bar
Failed To Load Connection - Qlik Sense 3.0.x - Feb2018
Failed To Load Connection - Qlik Sense 2.2
An Unknown Error Occurred - Qlik Sense 2.1.1 and 2.0.x
Browser Debug tools may display the following error in the console:
Data Market: entry-point-building.js??123145:62 API could not be reached.
The Qlik Sense DataMarket connector executable is cryptography signed for authenticity verification, and the .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally.
Qlik DataMarket connector will try to connect Internet to initialize and verify even without using it.
By making the changes in 3.x and June 2017 newer, Qlik Sense will not wait for a response on the verification step, which is the cause of the Failed To Load Connection and related error messages. It will also fix monitoring app issues and problems where the Data Load Editor loads forever. Note: it is highly suggested that all Qlik servers have internet access, however this will help to avoid some issues caused by it.
Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade.
1. Stop all Qlik Sense services on all nodes 2. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config 3a. If there is an empty <runtime/> tag, change it to
3.c If the <runtime> section has existing content, add generatePublisherEvidence.
<some other key="value"/>
4. Save machine.config 5. Repeat on all nodes (if applicable) 6. Start services on all nodes
1. Stop all services on all nodes 2. Open C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector\QvRestConnector.exe.config in an admin level Notepad window 3a. If there is an empty <runtime/> tag, change it to