topic Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.) in Connectivity & Data Prep

Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Wed, 27 Mar 2024 11:59:50 GMT

Hello experts,

There are connectivity problems in our site, which occurs on TASK relods only as far as we experienced. Its both occurs on ODBC & Rest connections.

When i check script logs we get this error immidiately after "Lib Connect to xxx" statement.

20240327T120257.655+0300 0023 LIB CONNECT TO 'SOME_ODBC_DB_Connection' 20240327T120339.724+0300 Error: Connection aborted (System error: The handle is invalid.) 20240327T120339.726+0300 Execution Failed 20240327T120339.730+0300 Execution finished.

the time from lib connect to statment and error differs from 30 to 150 seconds.

Btw <generatePublisherEvidence enabled="false"/> is set on all of our Qlik servers inside of <runtime> tag which is located on machine.config. We have to manually control the failed task list and manually send a re-start order to mitigate this, but its very exhausting effor to chase up a site with more than +2000 tasks. And this is still not a solution because sometimes its ends as a fail again, we always have to check if its finishes as success.

Qlik Sense Version: Qlik Sense February 2023 Patch 6 | 14.113.9

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

Nicolae_Alecu — Wed, 27 Mar 2024 12:11:19 GMT

Hello,

Check this article:

https://community.qlik.com/t5/Official-Support-Articles/Operation-and-License-Monitor-App-Fail-With-Error-Connection/ta-p/1713805

Best Regards,

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Wed, 27 Mar 2024 12:16:26 GMT

Hello @Nicolae_Alecu

This not helps 😞 as i mentioned on my post its already set on the machine.config settings.

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

Nicolae_Alecu — Wed, 27 Mar 2024 12:20:42 GMT

I just found this article, you can find here more suggestions:

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Tasks-fails-with-Error-Connection-aborted-System/ta-p/2413866

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Fri, 29 Mar 2024 13:54:01 GMT

Quick Summary for whom have same issue

We uninstalled following patches from server but its not fixed the problem.

kb5034767
kb5034614
kb5034862

In engine systemlogs there are 2 entries for this error but when i seached them in knowledgebase couldnt find that something helps. Are there someone knows what is the cause of reason 991&999 ?

CGenericConnection: Failed to send QVX_TERMINATE to process 3576 (reason 991); C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe CGenericConnection: Call to Terminate process 0 (reason 999) without open communications channel; C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

ms-roha — Tue, 02 Apr 2024 08:22:38 GMT

Hello,

we have the same issue in one of our customer environments (Qlik Sense Version November 2023). It also started after Windows Updates were installed last wednesday.

For us it seems like the OdbcConnectorPackage.exe can not start anymore. The logfile in C:\ProgramData\Qlik\Custom Data\QvOdbcConnectorPackage\Log contains the following error:

20240402T070009.990+02:00 ODBC [1] 7.22.0 FATAL QLIK-SENSE \\.\pipe\command_1cebdae2be995c990c2aa68648eb34cfecd6acf7.pip (null) (null) (null) (null) ODBC PipeName=\\.\pipe\command_1cebdae2be995c990c2aa68648eb34cfecd6acf7.pip Source=ODBC ReloadId=NA TenantId=NA UserIdType=NA UserId=NA EngineSessionId=NA AppId=NA RequestGuid=NA Message=Unhandled exception An exception was thrown while activating Qlik.Connectors.SDK.Common.Server -> Qlik.Connectors.Odbc.JSON.JsonRequestHandler..

Unfortunately, even changing the loglevel to ALL or DEBUG does not produce more detailed errors so we can only assume it has something todo with SSL/TLS issues.

I already tried a few things like using IIS Crypto to enable/disable TLS versions and protocols and changing machine.config file but nothing worked.

We plan to update Qlik Sense to the latest version tomorrow and if that doesnt fix the problem gradually uninstall Windows Updates until we find a working configuration.

Hope you keep us updated if you find something, will do the same!

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Wed, 03 Apr 2024 05:50:23 GMT

Hello Roha,

Thanks for your update, we also have a open ticket for this issue but no suggestions have been submitted yet. If i find anything new i will keep you informed.

have a nice day

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

ms-roha — Wed, 03 Apr 2024 16:07:23 GMT

Here again to report my findings:

* Update to the newest Qlik Sense Version (February 2024 SR2) did not fix this issue

* Uninstalling Windows Updates proved difficult because there were a lot and it would take a lot of time to restart / test after each uninstall, the ~10-15 I uninstalled didn't change anything though

* Regenerating Keys for the QvOdbcConnectorPackage and QvWebStorageProvider did not change anything

* I installed the QlikView OdbcConnectorPackage and tried to start it with a double click which atleast logged the following error (important part: "Could not get key with id prefix 'qseow'")

20240403T165229.503+02:00 ODBC [1] 6.211.0 FATAL QLIK-SENSE (null) (null) (null) (null) (null) ODBC PipeName= Source=ODBC ReloadId=NA TenantId=NA UserIdType=NA UserId=NA EngineSessionId=NA AppId=NA RequestGuid=NA Message=Unhandled exception An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = Server (ReflectionActivator), Services = [Qlik.Connectors.SDK.Common.Server], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = None, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = JsonRequestHandler (ReflectionActivator), Services = [Qlik.Connectors.SDK.Common.JSON.IJsonRequestHandler], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor(Autofac.IContainer)' on type 'JsonRequestHandler'. ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = GetInputOptionsCommand (ReflectionActivator), Services = [Qlik.Connectors.SDK.Common.Commands.GetInputOptionsCommand], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = None, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = OdbcMetadataService (ReflectionActivator), Services = [Qlik.Connectors.SDK.Common.Services.ISourceMetadataService], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = DefaultOAuthHelper`2 (ReflectionActivator), Services = [Qlik.Connectors.SDK.Common.OAuth.IOAuthHelper], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = FileSystemCachingService (ReflectionActivator), Services = [QlikView.Qvx.QvxLibrary.Services.ICachingService], Lifetime = Autofac.Core.Lifetime.RootScopeLifetime, Sharing = Shared, Ownership = OwnedByLifetimeScope ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'FileSystemCachingService'. ---> Could not get key with id prefix 'qseow' (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) (See inner exception for details.).

What "fixed" the issue for me is renaming/removing the directory "%APPDATA%/Qlik" which apparently stores the encryption keys for the connectors (I just renamed it to "-Qlik").

After I did that and restarted Engine & Scheduler service the data connections panel started to load again.

I also tested a reload that failed with "invalid handle" before and it did work. I'm not sure what that means for connectors that depend on the encryption keys (e.g. Sharepoint / OneDrive) (https://help.qlik.com/en-US/connectors/Content/Connectors_Home/Setting-encryption-key.htm) but that wasn't the case here.

Unfortunately, I cant access the Table-Selection Wizard or the Edit/Create dialog of the data connection.

I'm using a virtual proxy (/windows) for this environment, the default one (/) redirects to an external login page. When I press the edit/select data button in the data connections panel it ignores the virtual proxy and tries to load it from "/customdata/..." instead of "/windows/customdata" (which it does correctly for the other data connections, e.g. custom ODBC).

But maybe that is because I installed the QlikView versions of the OdbcPackage (I already uninstalled it, but it still could have changed something).

Guess we'll do another rollback and this time I'll just do the version update and folder-rename.

Hope this helps you.

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

ms-roha — Thu, 04 Apr 2024 06:58:26 GMT

I'm back to tell you that the solution doesn't seem to work.

Yesterday I was able to connect & successfully load tables from the database but today it fails again, this time with an "invalid username/password" message.

I already tried updating the data connection with the same credentials (in case Qlik needed to re-encrypt the credentials) but that also does not work.

This time, the following error is logged in the ConnectorPackage logfile:

System.Data.Odbc.OdbcException (0x80131937): ERROR [IM002] [Microsoft][ODBC Driver Manager] ...

I will probably create a ticket and see if Qlik Support has a solution for this problem.

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Thu, 04 Apr 2024 07:08:46 GMT

Hello Roha,

Thanks for your replies, i got that badpassword error too on qlik-native postgresql connections.

-Meanwhile im increased the log level to debug following this article if i find anything suspicious

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-How-to-turn-on-Engine-DEBUG-logs-for-Connector/ta-p/2152905

-and i will try to change following local policy settings

>Local Security Policy>Local Policy>Security OPtions> Network security: LAN Manager authentication level > Send LM & NTLM – use NTLMv2 session security if negotiated>restart server

but because of local policies are administered by different teams it will take time to make this change.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level

I will keep u informed if this works.

have a nice day

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

ms-roha — Fri, 05 Apr 2024 13:49:37 GMT

After a rollback, version update and again renaming the %appdata%-folder the tasks worked again and this time the kept working for the scheduled nightly reload. Lets see how long this keeps up.

So atleast my problem seems to have something todo with the OdbcConnectorPackage not being able to read the encryption key in the files of this folder. I could open them with notepad so I don't think the files were corrupted.

I think it has something to do with the encryption algorithm that is used encrypt/decrypt the key but I don't know enough about this to give a solid answer. Would love to know what exactly caused the problem.

Because renaming basically makes the package recreate the key (which can be verified in the log-file, it states "created new master key qseow_master_key".

Still having the virtual proxy issue with the data connection dialogs but I can atleast work around that somehow. Will probably look into that seperately.

I haven't tried your local policy solution yet - will maybe do that when I have more time.

Cheers

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

BTIZAG_OA — Mon, 08 Apr 2024 06:36:32 GMT

Hello Roha,

Today we have call with Qlik Support, they adviced us to change machince.config file like this.

generatepublisher key was at top before this.

Suprisingly it works fine for now hope it wont appear again. Im not sure which one fixed the problem, changing the position of the key or restarting the server.

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

seblabalyerr — Fri, 03 May 2024 10:32:46 GMT

Hi Everyone,

Is there any solution about this issue?

Thanks

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

ms-roha — Mon, 06 May 2024 10:46:38 GMT

Hello,

try renaming the "%APPDATA%/Qlik" folder (e.g. to "-Qlik" or "Qlik.Backup") and restart the services.

This should recreate the ODBC connector package encryption keys which means you will probably have to update the username & password of all ODBC data connections but atleast this worked for me.

Cheers

Re: Tasks failed as Error: Connection aborted (System error: The handle is invalid.)

FabioHud — Tue, 11 Feb 2025 15:25:05 GMT

I'm having the same problem.
In my case, there was an error in the native Databricks connection that uses the QvOdbcConnectorPackge. I created a connection to Databricks with ODBC. This way I didn't have to depend on QvOdbcConnectorPackge to run the loads.