Knowledge

[Andre_Sostizzo]

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.

Cause:

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.
 

Resolution:

Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade. 

Option 1:

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

<runtime>     
     <generatePublisherEvidence enabled="false"/>  
</runtime>

3b. If there is no <runtime/> tag, add the below anywhere above the closing </configuration> tag.

<runtime>
    <generatePublisherEvidence enabled="false"/> 
</runtime>

3.c If the <runtime> section has existing content, add generatePublisherEvidence.

<runtime>
  <some other key="value"/>
  <generatePublisherEvidence enabled="false"/>
</runtime>

Example:
 

4. Save machine.config
5. Repeat on all nodes (if applicable)
6. Start services on all nodes

 

Option 2:

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

<runtime>     
     <generatePublisherEvidence enabled="false"/>  
</runtime>

3b. If there is no <runtime/> tag, add the below anywhere above the closing </configuration> tag.

<runtime>
    <generatePublisherEvidence enabled="false"/> 
</runtime>

3c. If the <runtime> section has existing content, add generatePublisherEvidence.

<runtime>
  <some other key="value"/>
  <generatePublisherEvidence enabled="false"/>
</runtime>

4. Repeat on all nodes and repeat for 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\QvEssbaseConnector
• C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector
• 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.
 

[Filippo_Nicolussi_P]

Note that sometimes if the <runtime></runtime> section is empty  you find it in the form :

<runtime /> 

[Gabriel_Araya]

HI, I have the same error, in the 'Data Load Editor', the data connections it's just a spinning wheel that never seems to stop. We are with Qlik Sense 2020 Sept Patch 7. The server machine has internet connections. The option 1 was applied without success. The option 2 was applied without success. Any tips will be appreciated.

Gabriel

[john_oll]

Option 1 did not work.
Option 2 afterwards did not work, still incredible slow ...
do you need to do the same for the SAP-Connector configs, if installed?

[eclutario]

Having the same problem, we're with May 2021 Release Patch 3.

@Gabriel_Araya we're you able to fix your issue?

[Thomas_Vallée]

@eclutario make sure you don't have error(s) in the network tab in your browser dev tools. I had an "unknown error" showing up despite I had apply the options listed in this article. I also had an error in the engine logs: 

RestClient: HTTP request for url v1/connectors?xrfkey=ichBinEinBerlinR failed with error code 12175 (source: 5) 

This solution did the trick for me  (Qlik support provided it to me):

https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-Data-Load-Editor-quot-Unknown-Error-quot-Sou...

Hope this helps!

[john_oll]

Seems like I was finally able to fix the problem.

Problem was that it always took 1minute until data connections were loaded, both when entering script editor for the first time during a session and at random points afterwards.

What helped to identify the underlying problem was debug-view in Chrome ( Press F12). In that view an error for the Data Market showed up each time the connections finished loading. 

Solution was to remove Data Market folder from  C:\Program Files\Common Files\Qlik\Custom Data\

So if your server can't access the internet, I would recommend you remove that connector (and repeat that after each update).
Would be great if Qlik fixed this behavior, so the manual solution is no longer necessary in the future.

[janyf]

Hello 

On version QSE Feb2022 on server which is cut from internet , option 1 solve problems with long loading/not working connectors 

brgds 

Jan Farkas