Direct Access Data Gateway not working after upgrading to 1.5.2

[TLX-QlikView]

Hi all

We recently setup data gateway and everything was working with it. We were able to connect to SQL Server through the gateway. Today i upgraded the gateway to 1.5.2 The service is up and running. 

The old connection was not working, so

I created a new data gateway and tried to connect to database. It is not connecting

Status(StatusCode="Internal", Detail="Command testconnection returned non-success: Connection failed: Please check the values for Username‚ Password‚ Host and other properties.")

Please help out

regards

KRS

[Albert_Candelario]

Hello @TLX-QlikView,

Thanks for posting.

Could you kindly let us know what version of SQL Server are you connecting to and on what OS are those DB installed?

Thanks in advance for your collaboration.

Cheers,

Albert

[Kayleigh_Milewski]

I was having this same issue and was told by support to convert all of my data connections that are broken to the new ODBC (via Direct Access gateway) connector.

This has been confusing and time consuming, and not entirely reliable. I am only getting partial data loads on some of my tables with no explanation and several new errors in other cases. 

[Albert_Candelario]

Hello @Kayleigh_Milewski,

Thanks for your comment. If you are having challenges within the new Generic ODBC functionality do not hesitate to open a new post or keep working with our Support team via an opened case if you already have a case with us.

Could you kindly let us know what version of SQL Server are you connecting to and on what OS are those DB installed?

Thanks in advance for your collaboration.

Cheers,

Albert

[fmarvnnt]

ODBC Connection string MUST be specified in any case.

Also specific SQL syntax settings must be specified (using the Detect button if the SQL RDMS is not listed).

FMa

[guidog1]

Tengo el mismo problema...

Todo estaba Ok hasta el 17 de Septiembre, pero el Lunes 18 de Septiembre las Cargas de Datos empezaron a fallar.

Nos dimos cuenta en la Consola de Gestión del Tenant que el Qlik Data Gateway (QDG) estaba "DESCONECTADO" y a pesar de realizar reinicios del Servicio del QDG no logramos poder Conectarlo.

Sin embargo el Lunes 25 de Septiembre, al entrar al Tenant,  recibimos el siguiente mensaje: 

Procedimos a la Actualización y ya pudimos Conectar el QDG versión 1.5.2 . De hecho lo hizo inmediatamente después de la Actualización del QDG a la versión 1.5.2

Sin embargo ahora las Conexiones de Datos que existían a la Base de Datos de SQL Server marcan el error:

LIB CONNECT TO 'KLYNS FARMACIAS:klywdb06'
20230927T182952.539+0000 Error: Connector KLYNS FARMACIAS:klywdb06 not found (Requested endpoint could not be provisioned due to failure to acquire a load slot: The user does not have permission to the gateway (DirectAccess-0002)
20230927T182952.539+0000 LIB CONNECT TO 'KLYNS FARMACIAS:klywdb06')
20230927T182952.539+0000 Execution Failed
20230927T182952.541+0000 Execution finished.

El usuario que ejecuta la Carga de Datos tiene todos los permisos sobre el Espacio Compartido que contiene la Conexión de Datos, inclusive lo  intentamos con el Propietario del Espacio y también marca error...

Ya abrimos un Ticket de Soporte con nuestro Soporte de primer nivel, pero no hay respuesta aun... 

[Albert_Candelario · Accepted solution]

Hello all,

A new Direct Access version has been deployed, please do upgrade to version 1.5.3 and let us know if ti resolves your issue if not using a MS SQL server 2012.

Cheers,

Albert

[jda_bryan · Accepted solution]

Was having the same issue with our gateway after the recent mandated upgrade.  After v 1.5.3 installation and configuration, everything was working again as expected.   Thank you.

[marksouzacosta]

I'm having the exact same problem with 1.6.6.

Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)
Sep 24 2019 13:48:23
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 22631: ) (Hypervisor)

[marksouzacosta]

Ok. I have fixed that adjusting the Port number.
I ran the following query on my SQL Server to get the port number:

USE master
GO
xp_readerrorlog 0, 1, N'Server is listening on' 
GO

With that in hands, was just a matter of adding the correct port on the connection configuration.