Unable to connect to the gateway (DirectAccess-2006)

[arnbank]

Hi, start to use Qlik gateway, and few days a ago we start to get errors on our app reloads:

<Requested endpoint could not be provisioned due to failure to acquire a load slot: Unable to connect to the gateway (DirectAccess-2006)>

maybe someone saw such before? and know how to solve it.

[Albert_Candelario]

Hello @JOBrien,

I am glad you already have a support case with us. The issue you have been experiencing might be related to a different topic that the one described on this post.

What we can reassure you is that the engineering team is dedicated to ensuring our customers satisfaction with the Qlik Data Gateway product. We constantly strive to improve the product through frequent updates and defect fixes. And the next release, potentially planned for next week, should be including several improvement and fixes that might have a very beneficial impact on your current issue.

Cheers,

Albert

[NadiaB]

Hi @JOBrien 

The error can be caused for issues in Cloud side but also in the Data Gateway server.

Have you seen any connectivity errors in the DirectAccessAgent.log log , that log should show successful communication with QCS, if you see any errors there it is suggested to engage your network team and verified that they allowed HTTPS and WSS traffic over port 443 to both tenant alias hostname and the tenant (unique) hostname from the data gateway server. This information is in The About section in QMC, it will show tenant alias hostname and tenant hostname.

https://community.qlik.com/t5/Official-Support-Articles/Find-your-Qlik-Cloud-Subscription-ID-and-Ten...

You can also verify if the time of the communication issues matches the time you see the error in the other logs. 

Hope it helps!

[fmarvnnt]

Just to make U aware that it happened 3 times this morning on our production environnement with QDG 1.3  connected to SAP BASIS 7.40 SP 28.  Unique solution:  restart QDG service on prem.

Regards,

FMa

[Albert_Candelario]

Thanks for your feedback @fmarvnnt .

As mentioned the issue mentioned originally here had a well identified cause, hence you might be experiencing another issue that is provoking within the same error code.

It would be good to have such on a new post instead of posting on this old one.

Thanks for your collaboration.

Cheers,

Albert

[luizcdepaula]

Hi, 

We have been getting the same error. We are on the latest version of the QDG. We will be opening a case with Qlik, however, it seems that this issue has not been addressed completely by Qlik yet. Waiting on another resolution.

Thanks,

Luiz

[NadiaB]

Hi @luizcdepaula 

By any chance do you see any errors in the DirectAccess log ? We have seen those error in the past when there is a connectivity issue or an ODBC crash, best option would be to get the reload Id that is failing and then search for that reload id in the Data Gateway logs to see at what time was being executed, if you see that the odbc connector or the odbc connector agent logs show that the reload failed lets say at 7:21 am, then you can go back to the DirectAccess log and verify if there is an error at that time that can give some leads, it is also recommended to look at the Windows Logs. 

Logs are usually in the following path :

C:\Program Files\Qlik\ConnectorAgent\data\logs

Hope it helps !

[RamiSmt]

Hello Albert,

We are experiencing the same issue with our applications that use Qlik Data Gateway connectors (latest version). These applications have always worked correctly, but for the past few days, they are failing to load properly. We are receiving the following error message:

vbnet

Copier le code

Connector 0_CONNEXION_DONNEES:NEW MAGIC not found (Requested endpoint could not be provisioned due to failure to acquire a load slot: Unable to connect to the gateway (DirectAccess-2006) LIB CONNECT TO '0_CONNEXION_DONNEES:NEW MAGIC')

Connector 0_CONNEXION_DONNEES:NEW MAGIC not found (Requested endpoint could not be provisioned due to failure to acquire a load slot: Unable to connect to the gateway (DirectAccess-2006)

Steps we have taken to troubleshoot:

1. Reviewed the logs.
2. Restarted the Data Gateway services on the dedicated server.

Unfortunately, these steps have not resolved the issue.

We kindly request your assistance to identify and fix the problem as soon as possible.

Thank you for your prompt attention;

Rami

[diegomaz]

Hi,

A few weeks ago, I updated to version 1.6.6, and every day I encounter the same error with each data reload.
Is there any other solution?

Thanks in advance
Diego

[Albert_Candelario]

Kindly confirm that your reloads are not facing these issue anymore.

Cheers,

Albert

[FedericoC]

Today we have "

Connector xxxxxxxxxxx not found (Requested endpoint could not be provisioned due to failure to acquire a load slot: Command getReloadSlot error for reload xxxxxxxxxxxx. Success with empty url.

" Data Gateway 1.6.7 It's impossible works so: completly random.