article Data Gateway failing with Invalid metadata response (DirectAccess-2201) in Official Support Articles

Data Gateway failing with Invalid metadata response (DirectAccess-2201)

NadiaB — Mon, 25 Sep 2023 12:05:28 GMT

Qlik Data Gateway erroring out with "Invalid metadata response (DirectAccess-2201) " message. The error could be due to a different issues.

Resolution

Verify Privileges on the space where the Gateway was created and the Space where user is attempting to create the connection, our documentation describes the details here
If privileges are correct, try to restart Qlik Data Gateway services on the Server where it resides.
Verify if the issue is specific to a connection, if one user was able to successfully create a connection, attempt to create a new connection with the user that is getting the error.
If nobody is able to create a connection for an specific Data Source, attempt to configure a DSN ODBC connection from the Data Gateway Server to verify it succeeds.

Cause

The cause of the issue is usually configuration, if the suggestions above didn't fix the issue it will be necessary to report the issue for further analysis.

Environment

Qlik Data Gateway

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Thierno — Fri, 02 Sep 2022 15:59:04 GMT

Hi NadiaB,

I have the issue and I unblocked the port as said but it still doesn't work.
I've posted more detail in this post :

https://community.qlik.com/t5/Qlik-Cloud-Data-Services/Qlik-cloud-Data-gateways/m-p/1976446#U1976446

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

dennismachel — Mon, 12 Aug 2024 15:39:33 GMT

I am yet to start using Data Gateway because of this issue. I have reported to QLIK and still no resolution. Frankly, rather disappointing.

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

youngaaron — Wed, 18 Dec 2024 22:53:54 GMT

Hi @dennismachel - did you end up finding a solution for this? We are experiencing the same issue.

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Lemmyduke1 — Wed, 15 Jan 2025 14:47:18 GMT

Hi everyone, is there any solution for this issue?
I'm experiencing the same as above ("Invalid metadata response (DirectAccess-2201)"), followed all the steps and even checked that my remote desktop can reach the server. I told the customer also to check if 443 port is open.

Thanks!

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Steve_Nguyen — Wed, 15 Jan 2025 15:05:38 GMT

checking on this , many other customers try below and it resolve their issue :

The issue was identified after Run StartOdbcConnector.bat from a command line in '‘C:\Program Files\Qlik\ConnectorAgent\runOdbcConnector’'.
The issue was because of the .net version in the Data Gateway server. after upgrading .net from 6.0.21 to 6.0.29 then the issue is fixed.
----
Provided customer best practices Help entry and article https://community.qlik.com/t5/Official-Support-Articles/Data-Gateway-failing-with-Invalid-metadata-response-DirectAccess/ta-p/1975952. Customer installed Data Gateway Direct Access on a dedicated server and the issue was resolved.
----
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/direct-access-gateway-setting-up.htm
----
Make sure you have checked the article and ticked all of the boxes.
https://community.qlik.com/t5/Official-Support-Articles/Data-Gateway-failing-with-Invalid-metadata-response-DirectAccess/ta-p/1975952
If step 1 doesn't help, try to perform below steps.
- Remote access to the Data Gateway server.
- Open the folder path ‘C:\Program Files\Qlik\ConnectorAgent\runOdbcConnector’. Find the right path if you installed Data Gateway on another drive/folder
- Run StartOdbcConnector.bat from a command line and share the output.
From the output you will understand the root cause more clearly. Most of the issues was caused by the Microsoft .net version. For example, upgrade .net from 6.0.21 to 6.0.29 fixes the issue.
----

Qlik Data Gateway deployment are attached to a Space, and you need to have at least the Can view + Can Edit role in the space which is attached to this Data Gateway Deployment. If not you can't create a connector with this Data Gateway deployment.

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Lemmyduke1 — Wed, 15 Jan 2025 15:27:55 GMT

Hi Steven_Nguyen,

thanks for your support.
I executed the .bat file.

I think the important stuff is here:
fail: Microsoft.Extensions.Hosting.Internal.Host[11]
Hosting failed to start
System.IO.IOException: Failed to bind to address http://127.0.0.1:50060: address already in use.
---> Microsoft.AspNetCore.Connections.AddressInUseException: Only one usage of each socket address (protocol/network address/port) is normally permitted.
---> System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.

What does it mean? There's already a service or a Odbc connection using that port?

Thanks in advance!

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Sonja_Bauernfeind — Tue, 21 Jan 2025 09:41:54 GMT

Hello @Lemmyduke1

'address already in use' and 'Only one usage of each socket address (protocol/network address/port) is normally permitted' indicate that this port is already in use by a different process. You will need to investigate which one it is and troubleshoot accordingly.

For any further assistance, I recommend posting your requirement in the Connectivity and Data Prep forum, where our active product experts and your knowledgeable Qlik peers can better assist you.

All the best,
Sonja

article Data Gateway failing with Invalid metadata response (DirectAccess-2201) in Official Support Articles

Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Resolution

Cause

Related Content

Environment

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)

Re: Data Gateway failing with Invalid metadata response (DirectAccess-2201)