Note: This articles applies only to Qlik Sense versions 3.x
Qlik Sense 3.x has reached end of life. For assistance with newer version of Qlik Sense, see An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet
or Data Connections not loading in Qlik Sense
For the 3.x version, review the content of this article.
The user can not see or create data connections in the Data Load Editor. When he tries to Create a new connection through clicking on the "Create new connection" button a black bar appears and the list is not expanded with available connections as expected. When checking the developer tools in the browser Error: Failed to load resource, server responded with a status of 500 (Internal Server Error) can be seen. The issue is browser independent. Service restart does not help.
Issue may present itself as shown:
Other symptoms might include:
- ErrorCode.11041 occurs when opening up an App
- ErrorCode.11043 occurs when creating a Database connection in the data load editor.
The two symptoms will correlate with the Qlik Sense system having a restricted or no internet connection.Environment:
Qlik Sense 3.2 and later 3.x versions
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.
Edit the .Net Framework's machine.config file
- Stop all QS services on all nodes
- Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
Ensure the runtime entries are entered exactly
as seen below and follow in line with the other entries in the machine.config file. If the entries are tabbed differently, or indented too much or not at all, the changes may not solve the Data connection spinning problem.
Change (or add) the <runtime/>
tag to reflect:
If the <runtime>
section looks different, modify it to:
<OTHER CONFIGURATION="YOU VALUES">
- Save machine.config
- Repeat on all nodes (if applicable)
- Start services on all nodes
Changes to machine.config affects all software using the .NET framework feature.NOTE2:
3rd party connectors might be compiled for 32-bit platforms.
In such case repeat steps above for the 32-bit version of the machine.config file
Ensure that the Account running the Qlik Sense Services has the permission to write to the Log folder (at C:\ProgramData\Qlik\Sense\Log
Check the log files timestamps to see if they match the current date. If not:
- Give the account the correct permissions (right-click Log folder -> properties-> security)
- restart the QlikSenseDispatcher Service
Uninstalling 3.2 and installing 3.2 again and restoring repository database from manual backup.
You can temporarily remove or move to a different folder (outside of Program Files) the OvOdbcConnectorPackage
from the installation folder:C:\Program Files\Common Files\Qlik\Custom Data
In a multi node environment please do it for all the nodes.
After that you will not be able to use the Data Market Connector or the ODBC Pacakage. For ODBC connections you can use Native DSN.
Please see as well article: Data connections in Qlik Sense 3.1 not visible in Data Load Editor or ErrorCode 11041 / 11043