Joseph and Mark,
I have 4 clients running on 3.1.3 without any issues. And then monday I had 1 client with this issue. The client also has a domain and windows setup that is not very standard and seemed very badly configured. Like I could not run the services using a domain service account.
I'd be great if one of you could file this bug with qlik.
From qlik Support :
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 QMC 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 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.
Qlik R&D is evaluating options to mitigate the effect of restricted, slow or no internet connection for future releases of Qlik Sense.
Editing the .Net Framework's machine.config file
Stop all QS services on all nodes
a) If there is a <runtime/> tag, change it to
b) If there is other stuff in the <runtime> section, then change it to look like this:
Repeat on all nodes (if applicable)
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;
If you follow instructions and disable Microsoft .NET framework part it removes the error. Didn’t see anything else about this in release notes for 3.1.4. tho.
Med vennlig hilsen - Best regards,
Qlik Pre-Sales & Consultant
Fra: Carlos Silva
Sendt: 10. januar 2017 13:38
Til: Ali Ahmad <email@example.com>
Emne: Re: - Qlik Sense Error 11041
The problem is not resolved in 3.1.4 - I encountered it yesterday in 3.1.4 environment.
An alternative solution instead of disabling the function in the .NET framework is to configure a proxy server under internet options for the service user (under which the Sense services are running). If that is a possiblity at the customer site you are working at, that will also solve the problem. Obviously that will require that there are access to the outside world through a proxy - but it's at least worth checking just in case.
Hey, the issue still appears in 3.2.4 no resolution in sight. In addition to fix editing the .Net files. You also edit your connectors config:
Option 1: Editing the Connector configuration file:Stop all Qlik Sense services on all nodes
1. Open the config file in the connector folder in C:\Program Files\Common Files\Qlik\Custom Data\
for instance C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe.config 2. Add the following values before the closing </configuration> tag:
<runtime> <generatePublisherEvidence enabled="false"/> </runtime>
3. Repeat steps 2 and 3 for all nodes and 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\QvRestConnector\QvRestConnector.exe.config