An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet
Article Number: 000016310 | Last Modified: 2019/07/16
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. Un-doing an agreement to the Qlik DataMarket Terms of Service does not fully disable Qlik DataMarket. Moreover, certain functionality of DataMarket is active when the Terms of Services are not agreed to.
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:
An Unknown Error Occurred - Qlik Sense 2.1.1 and 2.0.x
Failed To Load Connection - Qlik Sense 2.2
Failed To Load Connection - Qlik Sense 3.0.x - Feb2018
The Hub has continuous bubbles while loading forever
You will likely also see these errors recorded in the Engine > System > Service log.
Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade.
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.
For Qlik versions 3.x AND June 2017 and newer... this will disable the validation step in DataMarket's initialization:
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 a <runtime/> tag, change it to <runtime> <generatePublisherEvidence enabled="false"/> </runtime> 3.b If there is other stuff in the <runtime> section, then change it to look like this: <runtime> <some other key="value"> <generatePublisherEvidence enabled="false"/> </some other key> </runtime>
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 3. Add the following values before the closing </configuration> tag: <runtime> <generatePublisherEvidence enabled="false"/> </runtime> 4. Repeat on all nodes and repeat for all .config files a - C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe.config b - C:\Program Files\Common Files\Qlik\Custom Data\QvDataMarketConnector\QvDataMarketConnector.exe.config c - C:\Program Files\Common Files\Qlik\Custom Data\QvSalesforceConnector\QvSalesforceConnector.exe.config d - C:\Program Files\Common Files\Qlik\Custom Data\QvEssbaseConnector e - C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector f - C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage
5. Start all services on all nodes 6. Validate
It may be necessary to include the key immediately before the runtime closing tag if there are many values in the runtime section.
For Qlik Versions 2.x.x [mid-2016 and older]... this will fully disable Qlik Sense DataMarket:
Remove OR reName the file on all nodes C:\Program Files\Common Files\Qlik\Custom Data\QvDataMarketConnector
NOTE: This folder is likely to be re-created upon upgrade.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.