ADBC - Unable to connect from Power BI Desktop (May) to Dremio Software (25.x)

1

Unable to connect from Power BI Desktop (May) to Dremio Software (25.x) through Power BI Gateway, regular ODBC without ADBC works ok

Followed instructions from here Microsoft Power BI with ADBC | Dremio Documentation but cannot connect getting below error. Tried swapping ports between 31010 and 32010 and no port but same error. Please help

Details: “ADBC: IOError [FlightSQL] [FlightSQL] connection error: desc = “transport: authentication handshake failed: credentials: cannot check peer: missing selected ALPN property. If you upgraded from a grpc-go version earlier than 1.67, your TLS connections may have stopped working due to ALPN enforcement. For more details, see: TLS does not enforce ALPN protocol · Issue #434 · grpc/grpc-go · GitHub” (Unavailable; GetObjects(GetDBSchemas))”

2

Hi @rdkworld ,

Just to start with some context:

  • PowerBI is using a ADBC driver compiled from golang. The go driver implements Flight SQL on top of grpc-go.
  • ALPN stands for Application-Layer Protocol Negotiation. It’s a TLS extension that allows a client and server to negotiate which application protocol to use during the TLS handshake.
  • As the message instructs, after 1.67 grpc-go started enforcing ALPN h2 support for the TLS connections.

Check for ALPN h2 support on your endpoint with the following command line:
openssl s_client -connect dremio-endpoint:32010 -alpn h2
and look for ALPN protocol: h2

Ideally the best solution would be to configure your server configuration to support ALPN. As an example, I configured my AWS NLB with a TLS listener on the port 32010 with HTTP2Only (docs).

As a fallback, you can try to set the environment variable GRPC_ENFORCE_ALPN_ENABLED to false, I tested this on my NLB without ALPN. Notice that this seems to be a temporary solution for few more releases of grpc-go.

3

Hi @Helder_Gregorio
Thank you for detailed context and some suggestions, I checked ALPN h2 support on Dremio endpoint (AWS 25.x) as suggested in your command and it did return ALPH protocol: h2, so i guess we are good there.

Interesting thing is I tried again from Power BI Desktop to Dremio with adbc on port 32010 and it indeed was able to fetch data from Dremio using Arrow client which is what I wanted in first place.

However, before I publish to Power BI service, when I go to configure gateway for 32010 for adbc, it fails with below error
Unable to create connection for the following reason: Unable to connect to the data source. Either the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid. Please verify the data source configuration and contact a data source administrator to troubleshoot this issue.

Details:

CustomerO365DataGateway_03: ODBC: ERROR [08S01] [Microsoft][Drill] (20) Failure occurred while trying to connect to local:32010=dremioinstance.com.com. (Details: [30001]Connection failure. Host:dremioinstance.com.com port:32010. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

FarmersO365DataGateway_02: ODBC: ERROR [08S01] [Microsoft][Drill] (20) Failure occurred while trying to connect to local:32010=dremioinstance.com.com. (Details: [30001]Connection failure. Host:dremioinstance.com.com port:32010. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

FarmersO365DataGateway_001: ODBC: ERROR [08S01] [Microsoft][Drill] (20) Failure occurred while trying to connect to local:32010=dremioinstance.com.com. (Details: [30001]Connection failure. Host:dremioinstance.com.com port:32010. Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

Please have this information handy if you choose to create a support ticket.

Session Id: 852c9d9d-a3af-4f63-b068-c0a764eb1df0

RequestId: b4faa7bb-1862-452c-8dfe-288ea98b260d

Cluster URI: https://api.powerbi.com

Status code: 400

Time: Mon Jun 02 2025 18:49:40 GMT-0700 (Pacific Daylight Time)

but when I change the port to 31010 (with adbc:// or regular) it goes thru as before but thru ODBC not Arrow client

So, wondering why Power BI gateway is not able to connect to Dremio over ADBC 32010, all required ports were open from gateway to Dremio

4

Interesting thing is I tried again from Power BI Desktop to Dremio with adbc on port 32010 and it indeed was able to fetch data from Dremio using Arrow client which is what I wanted in first place.

Great, so connecting to Dremio using ADBC is working with PBI Desktop.

However, before I publish to Power BI service, when I go to configure gateway for 32010 for adbc, it fails with below error
Unable to create connection for the following reason: Unable to connect to the data source. Either the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid. Please verify the data source configuration and contact a data source administrator to troubleshoot this issue.
…
but when I change the port to 31010 (with adbc:// or regular) it goes thru as before but thru ODBC not Arrow client
So, wondering why Power BI gateway is not able to connect to Dremio over ADBC 32010, all required ports were open from gateway to Dremio

  • CustomerO365DataGateway_03: ODBC: ERROR [08S01] [Microsoft][Drill] (20) Failure occurred indicates that the driver being used is the ODBC Simba Drill and not ADBC Flight SQL. It also seems to indicate a timeout
  • If it works on 31010 with the adbc:// prefix, I may assume it is not latest one and probably doesn’t have a new connector with the ADBC support.
  • Is it possible that PowerBI Gateway is not up-to-date? We would recommend to update PowerBI Gateway to April 2025 (only Dremio Software support)
    • You can also update to May 2025 but we found a issue that’s was fixed for June 2025. We’re waiting for June 2025 to be released by Microsoft (more details on the issue: cloud, software)
5

Thanks again @Helder_Gregorio for your quick responses, appreciate it. We will wait for June 2025 Power BI Gateway to be released and then install and re-test to avoid April 2025 Gateway version. I will circle back at that time if this is still an issue after the upgrade. Thanks again!