Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Data Gateway Direct Access disconnections (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.

100% helpful (2/2)
cancel
Showing results for 
Search instead for 
Did you mean: 
NadiaB
Support
Support

Data Gateway Direct Access disconnections (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.

Last Update:

Jul 8, 2024 8:24:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

May 21, 2024 3:12:18 PM

The data connection between Qlik Data Gateway - Direct Access and Qlik Cloud may occasionally fail due to network connectivity issues. 

Commonly, the disconnects are short, and the data connection will recover automatically without the Qlik Sense app reload failing. 
Longer connection interruptions may lead to a failed Qlik Sense app reload. 

Connection failure can be seen in DirectAccess.log at the time of failed connection, regardless if the app reload is successful or not:

[Service ] [ERROR] Connection failed
System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.

Resolution

Install Qlik Data Gateway - Direct Access 1.6.6 or later. 
Configure Data Gateway following recommendations documented in Qlik Help. 

Qlik Data Gateway has an automatic re-connect mechanism that restores failed connections and allows the Qlik Sense app reload to continue without the app reload failing. 

If Qlik Sense app reload is not failing due to data gateway connection failure, the connection failed error can be ignored. 
If the Qlik Sense app reloads fails due to a longer data gateway connection failure, it will typically reload successfully on the next scheduled or manual reload. 

For business-critical apps, it is possible to mitigate the impact of data gateway connection failure by implementing app-level reload resilience. This can be accomplished by using Qlik App Automation for reload with a retry mechanism and script-level retry for failed load statements, retrigger reload tasks from external tasks through API, etc. 

Cause 

A WebSocket connection is used between Qlik Data Gateway - Direct Access and Qlik Cloud. This persistent connection may fail I any network device in the routed path fails to keep the connection alive through the entire data load. 

Data Gateway connects to Qlik Cloud through a private network(s), the public Internet, and Qlik Cloud infrastructure. Daily connection failure is not unusual on a low level in this complex connection path. 

Related Content

Qlik Data Gateway - Direct Access. Reloads failing intermittently

Qlik Application Automation: How to automatically rerun a failed automation

Internal Investigation ID(s)

QB-25723

Environment

  • Data Gateway Direct Access
Labels (1)
Version history
Last update:
2 weeks ago
Updated by: