Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
I have just upgraded to the latest version of Sense (Sense June 2017).
We have an issue when opening the load editor. The "connections" on the left hand side takes a minute or so to turn up..
The problem is related to this : https://qliksupport.force.com/QS_CaseWizardKnowledgeArticle?Id=ka5D00000004S6RIAU
The server has no internet access and the DataMarket connector wants to access the internet... That is why ..I do not get any errors like the article describes.. Just the long wait... 🙂
I have done as suggested in the article, but it does not help... (with the Machine.config in .net framework) and in the config files for the connectors in the C:\Program Files\Common Files\Qlik\Custom Data\
The services stopped and started...
Other than enabling access to the internet from the server, does anyone know how to avoid this?
Can you download the article and attach here, because the link you shared is only accessible to you and not others.
We are having the same issue. after upgrading to June Patch 1
actually our issue is worse, since yesterday it took ~20 minutes for the connections to apeear,
but today they don't show up even after an hour...
We have opened a case at Qlik Support, and it is being escalated to R&D.
Do you still have this issue?
In our case Qlik R&D concluded that the problem is related to two of the connector packages that Qlik distributes.
The solution/workaround in our case was to delete the folders "QvOdbcConnectorPackage" and "QvDataMarketConnector"
from the C:\Program Files\Common Files\Qlik\Custom Data folder.
and then restart the Engine.exe process.
Just make sure you keep a copy of the folders you delete, if you want to add them back!
In our case this workaround does not have any drawbacks, since we do not use the Odbc-connectors Qlik provide, and not the Datamarket connector.
Note that you can still use Odbc-connectors you added via Windows ODBC Data Source Administrator, the deleted "QvOdbcConnectorPackage" has nothing to do with those ODBC connetions.
Download an IBM DB2 ODBC driver, install and use that.
(We don't use any IBM DB2 sources, but we do the equivalent for Postgresql, Hadoop and Sql Server)