Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.

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

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

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

Last Update:

Feb 2, 2024 5:30:17 AM

Updated By:

Rakesh_HB

Created date:

Feb 2, 2024 6:04:46 AM

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

Unknown Connection Type - ODBC.png

Unknown Connection Type - REST.png

 

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

  1. Stop all Qlik Sense services on all nodes.
  2. 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>​
  3. Save machine.config
  4. Repeat on all nodes (if applicable)
  5. 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:

Error 1053.png

Config file error.png

 

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

 

Related Content

Operation and License Monitor App Fail With Error: Connection aborted (System error: ***) 

Qlik Sense: "Error 1053: The service did not respond to the start control request in a timely fashio... 

Qlik Sense Repository Service stops automatically 

 

Environment

 

Labels (1)
Contributors
Version history
Last update:
‎2024-02-02 05:30 AM
Updated by: