article Qlik Sense Tasks fails with Error: Connection aborted (System error: The handle is invalid.) in Official Support Articles

Qlik Sense Tasks fails with Error: Connection aborted (System error: The handle is invalid.)

Rakesh_HB — Fri, 02 Feb 2024 11:04:46 GMT

Qlik Sense tasks fail except the Tasks associated with the Folder connection.

This issue can be identified by reviewing the Qlik Sense Script logs (How to find the Script (Reload) logs in Qlik Sense Enterprise on Windows).

Error: Connection aborted (System error: The handle is invalid.)
Execution Failed
Execution finished.

Qlik Sense data connections will show the following error,

Unknown Connection Type. QvOdbcConnectorPackage.exe

Unknown Connection Type. QvRestConnector.exe

To troubleshoot and identify the issue, review the Qlik Sense System Repository Trace logs (How To Collect Log Files From Qlik Sense Enterprise on Windows). Look for:

Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it has already been disposed.

Resolution

Option 1

Qlik Sense ODBC Connectors are no longer available after an Upgrade

Option 2

Stop all Qlik Sense services on all nodes.
Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
1. If there is a <runtime/> tag, change it to
  <runtime> <generatePublisherEvidence enabled="false"/> </runtime>
2. If there is other stuff in the <runtime> section, then change it to look like this:
  <runtime> <some other key="value"/> <generatePublisherEvidence enabled="false"/> </runtime>
Save machine.config
Repeat on all nodes (if applicable)
Start Qlik Sense services on all nodes

Make sure you have the exact same copy of "machine.config" file on all the Qlik Sense Windows machines.

This setup is required every time after Qlik Sense upgrading.

If failed to update/modify, it will not be possible to Start the Qlik Sense services on the non-modified Qlik Sense Windows machines, and the following error will be displayed:

Option 3

Restore the Last Known good configuration of Windows server backup (machine snapshot).

Possible Root Causes

The QvOdbcConnectorPackage.exe has been corrupted or is no longer present on the system or has otherwise become unusable.
The Connector executables are cryptographically signed for authenticity verification. The .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally. The connector will try to connect to the Internet to initialize and verify even without using it.
Windows Patches
Microsoft .NET Framework updates
Microsoft Visual C++ <version> Redistributable updates
Windows Registry changes