Creating a dataflow using gen1 and odbc while connecting to hive database

Hi ssewanyanaherbe,

Thanks for reaching fabric community. I can certainly understand how frustrating it is when your ODBC connection tests perfectly fine locally, but fails the moment you try to publish a Dataflow. That specific error code (DMTS_PublishDatasourceToClusterErrorCode) usually indicates a "handshake" issue between the Power BI Service and your Gateway cluster.

Since you are using a specialized Treasure Data Presto driver with SSL enabled, I would recommend checking these three areas:

• Try a DSN-less Connection String: Sometimes the Power BI Service struggles to resolve a local DSN name defined on the Gateway. Try using the full connection string directly in the Power Query source step. It should look something like this: Driver={Treasure Data Presto ODBC Driver};Host=[Host];Port=[Port];AuthenticationType=[Auth];SSL=1;

• Gateway Service Account Permissions: Since SSL is mandatory for your database, ensure that the Windows Service Account running your On-premises Data Gateway has the necessary permissions to access the SSL certificates on that machine. A connection can work for you locally but fail for the Gateway Service if it doesn't have the same certificate access.

• Update the Gateway: With the recent March 2026 updates, there have been some refinements in how Dataflows communicate with ODBC drivers. Ensuring your Gateway is on the latest version can often resolve these "Unknown errors" from external services.

One quick question: Have you had a chance to try this via Dataflow Gen2? It often provides more granular logs for ODBC connections and might give us a clearer picture of where the handshake is failing.

I hope this helps get your Hive data flowing! Please let us know if the connection string change works for you.