Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
The problem investigation has concluded that the connector execution error popups observed by some customers were due to OCSP/CRL network requests on connector process initialization, to verify Authenticode signatures on the connector executables.
These network requests can hang in a restricted network environment that drops packets instead of rejecting connections outright.
That causes the connector process to hang before connecting to its named pipe, which causes Engine to time out after 30 seconds waiting for the named pipe to be connected, which causes a “Failed to load connection” popup. That can occur quite apart (30 seconds later) from the connector invocation that causes it, which is extra confusing to users and gives the user ErroCode.11041
The problem is related to Bug QLIK-66335.
There is no specific solution that solves the issue. You can try the following:
- open up the connection for some time and let Qlik Sense connect
- upgrade to the latest version 3.2
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.