Solved: Re: Dataflow Gen2 with ODBC Source from onPrem Gat...

Data-Crunch · ‎09-25-2025

Hi all

I am stuck here with an issue for which no MS article was able to offer any insight. I have a DataFlow Gen2 with ODBC Queries that run via the onPrem Gateway. I am aware of the following limitations: On-premises and virtual network data gateway considerations for data destinations in Dataflow Gen2 -...

But even If I bring in only one query, and no other references, the publishing works, but the refresh fails saying the gateway is of the wrong version.
There was a problem refreshing the dataflow, the gateway version you are using is not supported. Please update to the latest on-prem gateway version and try again

The Gateway is running version 3000.182.5 (Sept 2025) so that can't really be the issue here.

If I bring in more queries with references to each other, the publishing fails with no error message at all...

Has anyone ever come across this issue before? Any common things I could check to find the root cause?

Thanks for the help!

v-tsaipranay · ‎09-28-2025

Hi @Data-Crunch ,

Thanks for reaching out to the Microsoft fabric community forum. Also thank you @vivien57 for your response.

Your gateway version (3000.182.5) is current, so the “unsupported version” error may be related to the gateway mode or registration. Please confirm it’s set to Fabric mode and try a clean reinstall if necessary. Also, check that TCP 1433 access to *.fabric.microsoft.com and *.dfs.fabric.microsoft.com is enabled, though network issues are unlikely since single queries are publishing successfully.

Note that Dataflow Gen2 has limitations with multi-query references when using ODBC sources, which can lead to publishing or refresh errors. To diagnose, enable both gateway logs and Dataflow diagnostic logs. As a workaround, consider splitting complex queries into separate dataflows and combining results later, so each can refresh on its own.

Hope this helps. Please feel free to rech out for any further questions.

Thank you .

View solution in original post

v-tsaipranay

Hi @Data-Crunch ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

v-tsaipranay · ‎10-08-2025

Hi @Data-Crunch ,

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided. If you still require support, please let us know, we are happy to assist you.

Thank you.

v-tsaipranay · ‎10-05-2025

Hi @Data-Crunch ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

v-tsaipranay · ‎10-02-2025

Hi @Data-Crunch ,

Yes, there is documentation that explains the limitations you're encountering which details how query references and network access (especially port 1433) affect refresh behavior in Dataflow Gen2 with on-prem gateways. Please refer the following:

For ODBC-specific setup and troubleshooting, please refer the following documentation : Set up your Odbc connection - Microsoft Fabric | Microsoft Learn

If you're still seeing refresh failures with a standalone query, I recommend verifying DSN configuration and gateway mapping. Also checking for reserved column names and enabling diagnostics in the service and gateway logs.

For more detail information look into the following documentation for better understanding: Data Factory limitations overview - Microsoft Fabric | Microsoft Learn

Hope this helps. Please feel free to rech out for any further questions.

Thank you .

v-tsaipranay · ‎09-28-2025

Hi @Data-Crunch ,

Thanks for reaching out to the Microsoft fabric community forum. Also thank you @vivien57 for your response.

Your gateway version (3000.182.5) is current, so the “unsupported version” error may be related to the gateway mode or registration. Please confirm it’s set to Fabric mode and try a clean reinstall if necessary. Also, check that TCP 1433 access to *.fabric.microsoft.com and *.dfs.fabric.microsoft.com is enabled, though network issues are unlikely since single queries are publishing successfully.

Note that Dataflow Gen2 has limitations with multi-query references when using ODBC sources, which can lead to publishing or refresh errors. To diagnose, enable both gateway logs and Dataflow diagnostic logs. As a workaround, consider splitting complex queries into separate dataflows and combining results later, so each can refresh on its own.

Hope this helps. Please feel free to rech out for any further questions.

Thank you .

Data-Crunch

Hi @v-tsaipranay I was able to solve the issue. It was indeed the gateway version which was still very old on another Gateway which I did not realize was involved. Thanks for all the pointers!

Data-Crunch · ‎09-29-2025

Thanks @v-tsaipranay and @vivien57
The status of the gateway is being checked now, thanks for the tips. As for the ODBC Limitations, is there any documentation on that? With a simple, standalone query, the publish succeeds, but the refresh fails... this is why I am so confused.
Thanks!