How to schedule a Refresh using PowerBI on-Prem Gateway using an adbc:// Dremio Connection – Dremio Support

Summary

The Power BI On-premises Data Gateway[1] is a bridge between Power BI in the cloud (Power BI Service, Fabric[2]) and data sources that live inside your network (on-premises or in a private cloud/VNet).

In a Dremio deployment, the Power BI On-premises Data Gateway is the bridge that lets Power BI Service (cloud) talk to Dremio Software[3] running inside your private network, when Dremio is not directly reachable from the internet.

Reported Issue

When attempting to schedule automatic Power BI Service dataset refreshes against a Dremio 26.1.5 on-premises cluster routed through the Power BI On-Premises Data Gateway (v3000.310.1), queries fail intermittently with the following error:

ChannelClosedException: [USER]: Channel closed
/10.162.0.133:31010 <--> /10.162.3.52:29963 (user client)

The connection path is: Power BI Service → On-Premises Data Gateway → Azure Load Balancer → Dremio Coordinator (port 31010).

The failures occur randomly across different tables during a report refresh, with longer refreshes (those triggering many sequential queries) being most susceptible. Affected jobs are marked FAILED in the Dremio UI despite data having been fully delivered to the client — Dremio's own ReAttemptHandler confirms this:

cannot re-attempt the query, data already sent to the client

The root cause is that the Azure Load Balancer's default TCP idle timeout (4 minutes) silently drops long-running Flight connections mid-transfer. The client then closes the socket before completing the TLS close_notify handshake, causing Dremio to register a failure on the connection teardown rather than on the query itself.

A secondary issue arose when the customer attempted to migrate from the legacy ODBC connector to ADBC (Arrow Flight SQL) following Microsoft's deprecation announcement: no documentation covered how to configure the On-Premises Data Gateway specifically for ADBC connectivity, leaving scheduled refreshes broken even after the driver change.

Overview

The gateway runs on a Windows machine (VM or a physical workstation) inside your network that can reach your Dremio on-prem cluster e.g. coordinator hostname, Flight SQL / ADBC on port 32010.

ADBC (Arrow Flight SQL) is the transport Dremio and Microsoft recommend, Microsoft is retiring as well the legacy ODBC driver for Dremio in Power BI and replacing it with Apache Arrow Database Connectivity (ADBC). This change affects Power BI Service first, Power BI Desktop and On-premises Data Gateway as per this announcement[4].

Relevant Versions Tools and Integrations

Dremio Software (on k8s) 26.1.8-202605070149260956-31448f13

MS Windows 11 (X64 - 25H2 - Build 26200.8655 + last hotfixes)

MS On-Prem Gateway v3000.322.4 (June2026)

MS Fabric PowerBI (cloud https://app.powerbi.com/) SV:13.0.28505.396, CV:2606.2.29748-train)

Steps to Resolve

1- Connect the On-Prem gateway to your MS account:

1- connect your onPrem gateway to your MS account.png

2- Once connected as per the above screenshot confirming the gateway is "online and ready to be used" you should see the Gateway available on the app.powerbi.com Dashboard under the On-premises data gateways tab:

2- once connected as per -1- status you should see the Gateway availlable on the app.powerbi.com Dashboard.png

3- In the navigation pane on the left side of your screen, click Workspaces and Create a "Semantic model" then Get data:

3- go to your workspace and create as example a Sematic Model and click on get data.png

4- Then choose your data source, e.g. Dremio Software:

4- choice your data source, e.g Dremio sw.png

5- Use the adbc:// protocol when entering the On-Prem cluster endpoint (Dremio Server), make sure to select your PBI On-Prem Gateway (from Step 2), then add your dremio credentials as applicable, and hit next

5- use adbc-:: , select your gateway, add your dremio credentials, and hit next.png

6- Select the tables / views to load

6- choice your table.png

7- Load the data, and once your work on the model is done, save it:

7- once your job is done, save the model.png

8- The model will appear in your workspace, open the dataset's scheduled-refresh settings:

9- Configure and enable the refresh schedule, selecting your timezone, schedule interval, and then apply:

9- go down to refresh, select your timezone, and the schedule interval, and click apply.png

10- You can see the next refresh schedule directly in your workspace:

11- Verify a successful refresh in Refresh history:

11- you can see when the refresh kick in the evidence in the dashboard, and you can see it as well from the refresh history tab- 2.png

12- Under Refresh history you can see the details of the scheduled execution:
12- once completed you can see as well the details of the schedule execution from Refresh history.png

Additional Resources

[1] https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem

[2] https://learn.microsoft.com/en-us/fabric/fundamentals/microsoft-fabric-overview

[3] https://docs.dremio.com/current/get-started/

[4] https://support.dremio.com/hc/en-us/articles/51909425120027-Announcement-Power-BI-Service-connections-migration-from-ODBC-to-ADBC