The refresh of the on-premise SQL connector is failing in Dataflow Gen1 within the Pro workspace

[Iras]

Dear Community Members,

I am using Dataflow Gen1 in the Pro workspace of the Power BI service to connect to an on-premise SQL Server database. A few months ago, everything was working fine. However, for the past couple of months, the refresh has been failing. When I refresh the data from the M-Query of the dataflow it works but when I refresh the dataflow it's failing.

In the error message export from the dataflow nothing is specified. it says ony Error : Request ID :  and Activity ID. 

Here are the steps I have thoroughly checked:

1. No premium transformations or features are used in the dataflow. I even tried using a basic table with 100 rows without any transformations, but it still failed.
2. I checked the Gateway connection configuration. It is working fine, as the same Gateway connection is being used to refresh the dataset, and it works.

3. The on-premises data gateway is up to date.

4. I recreated the dataflow multiple times in different Pro workspaces with different users and still the issue is persists. 

5. I also checked that,  the same dataflow is working perfectly fine when I use the Premium workspace. 

Has anyone experienced a similar issue or have any suggestions for a solution?

[Iras]

Dear @Anonymous 

1. The on-premises data gateway is up to date.

2. I recreated the dataflow multiple times in different Pro workspaces with different users and still the issue is persists. 

3. I also checked that the same dataflow is working perfectly fine when I use the Premium workspace. 

I still don't understand why it's creating issue only for on premise SQL server. 

[Anonymous]

Hi @Iras ,

Thanks for reaching out to our community.

Please verify that the on-premises data gateway is up to date. 

Please double-check the network and firewall settings to ensure there are no new restrictions or changes that might be blocking the dataflow from accessing the SQL Server.

Or recreate the dataflow from scratch with the same settings to see if the issue persists. Sometimes, configurations can become corrupted.

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.