Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
After having created a lakehouse on a fabric workspace we are trying to feed it using data coming from a SQL Server on promise. For this purpose (and following MS documentation) we have created a DataFlow Gen2. After having created the gateway connection we are able to reach SQL Server tables. Once we push the "Publish" button following error is triggered
Error message is clear, but we have updated our PBI gateway to the latest version available
even more we have configured the proxy/firewall to manage the outbounds connections as required here
https://learn.microsoft.com/en-us/fabric/data-factory/gateway-considerations-output-destinations
What is going wrong with the gateway when creating Dataflow Gen2? We are using same gateway on Dataflow Gen1 withou any issue,
Thx
Alfons
@alfBI : Thanks for replying back and apoloziges for not being clear . I do understand that the DF gen1 is working fine with the gateway , but DF gen2 is not . The intend to for the suggestion above to try to run it from the gateway machine was to see if we get get info on the error logs . Not sure if you got a try that out yet .
Hi, we are using succesfully same gateway on dataflow gen1 without isssues as well on other scenarios, so we are quite sure that the gateway works properly on other scenarios
Hi @alfBI ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
Otherwise, will respond back with the more details and we will try to help.
Thanks
Hello @alfBI
Thanks for using the Fabric community.
From what appears from the ask is your facing issues after you publish the reports .
Have you tried to refresh the report from the gateways machine . If not can you please give that a try as called out here
Although it isn't a guarantee of a successful refresh through the gateway, a successful Power BI Desktop refresh from the gateway computer is a strong indicator that everything is configured correctly on the gateway computer. In other words, if you can't refresh in Power BI Desktop from the gateway computer, it's highly unlikely that a refresh through the gateway will succeed. After a successful refresh in Desktop, you can narrow your troubleshooting steps to the configuration of the datasource and the dataset in the Power BI Service.
Thanks
HImanshu
Hi,
It looks I have adressed the problem after signing my account on the (it looks like this step is required to register the new version of the gateway on the service
Unfortunately my problems to consume on-premise data using the dataflow gen2 does remain.
Now after having created the dataflow gen2 (from the datalake) the destination does appear empty and there is now way to connect to the datalake
I suspect that the problem might be related with the following error message that does appear when connecting my dataflow gen2 to the gateway
Any idea about what is happening?
Thx
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
5 | |
4 | |
2 | |
2 | |
2 |