Skip to main content
Announcements
Qlik and Talend Support Cases are now opened in the same place.

Data connections in Qlik Sense not visible in Data Load Editor or ErrorCode 11041 / 11043

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Data connections in Qlik Sense not visible in Data Load Editor or ErrorCode 11041 / 11043

Last Update:

Aug 26, 2024 7:51:50 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 1, 2017 8:29:39 AM

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.

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 an online resource if the system doesn't have a cached local copy. These requests will timeout due to a lack of access to online resources in environments with restricted, slow or no internet connection. Due to the authenticity check failure, the connector will not run, and the app reload fails.

 

Resolution:

 

Edit the .Net Framework's machine.config file

  1. Stop all QS services on all nodes
  2. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config

    Change (or add) the <runtime/> tag to reflect: 
    <runtime>     <generatePublisherEvidence enabled="false"/> </runtime>​
    If the <runtime> section looks different, modify it to:
    <runtime>
      <OTHER CONFIGURATION="YOU VALUES">
        <...>
      <generatePublisherEvidence enabled="false"/>
    </runtime>​
  3. Save machine.config
  4. Repeat on all nodes (if applicable)
  5. Start services on all nodes


NOTE1: 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;
C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config
 
 

Labels (1)
Contributors
Version history
Last update:
yesterday
Updated by: