Forum Discussion
Gateway Connectivity Error
Hi,
I have got VNET gateways configured here, there and everywhere, that we use to connect to private data sources. We have been using them for some time now for both semantic models and Data Flows Gen 2. Recently, they stopped working for Data Flows Gen 2. To make things even more interesting, they work in DF edit mode in the service, but once published they throw this error:
"There was a problem refreshing the dataflow: 'Something went wrong, please try again later. If the error persists, please contact support.'. Error code: GatewayConnectivityError. (Request ID: 3cd21a08-xxxxx-xxxxxx-xxxxxxxx)."
It's the same issue across many different VNET gateways. They still work fine with semantic models though.
Gateway logs just say can't connet to DB.
Has anyone got any idea what may be going on?
Appreciate any help as I have run out of options here.
Thank you,
WJ
Hi wojciech ,
I think you can do these steps below:
1. Verify that all necessary IP ranges used by Dataflow Gen2 service are allowed in your network firewall settings. Microsoft provides a list of IP addresses that Power BI uses, which may differ slightly for Dataflow Gen2.
2. Dataflow Gen2 might require the use of the TDS protocol (TCP over port 1433) to read data from the staging Lakehouse before copying it to the desired data destination. Ensure that this port is open and accessible.
3. Sometimes, more detailed error messages can be found in the Power BI Service logs. Go to Settings > Manage Gateways > VNET Gateway Logs and look for any errors or warnings related to the dataflow refresh.
4. You can also look at this two documents:
Dataflow gen2 with Virtual Machine Gateway refresh... - Microsoft Fabric Community
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
4 Replies
Hi wojciech ,
I think you can do these steps below:
1. Verify that all necessary IP ranges used by Dataflow Gen2 service are allowed in your network firewall settings. Microsoft provides a list of IP addresses that Power BI uses, which may differ slightly for Dataflow Gen2.
2. Dataflow Gen2 might require the use of the TDS protocol (TCP over port 1433) to read data from the staging Lakehouse before copying it to the desired data destination. Ensure that this port is open and accessible.
3. Sometimes, more detailed error messages can be found in the Power BI Service logs. Go to Settings > Manage Gateways > VNET Gateway Logs and look for any errors or warnings related to the dataflow refresh.
4. You can also look at this two documents:
Dataflow gen2 with Virtual Machine Gateway refresh... - Microsoft Fabric Community
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi I am currently having this issue as well on the 23/04/2025 what exactly was the solution to the problem? Many thanks
We’ve managed to find a fix! One of our engineers was looking into a different issue and inadvertently fixed the issue we are seeing with the Gen2 Dataflow.
We have a Private DSN Zone for “privatelink.pbidedicated.windows.net” and our engineer enabled the setting “Fallback to internet”:
However, this is not a permanent fix and our infra team is still chasing microsoft to provide recomendations on that.
