Dataflow Refresh Failing gateway version you are using is not supported

(1) Share

Report

Posted on by JJ-27101724-0

Hello,

We previously had a dataflow hitting a SQL server with the with a refresh schedule. The refresh was working successfully until recently where we get the below error.

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. (Request ID: d351d9ab-1291-48cc-91d0-b55ee9b87b16).

We have upgraded the data gateways to the most recent version but still are having the same error. Any ideas?

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 2,487 on at

Like (0)

Report
Copy link

Link copied!
Information that would help narrow this down

Is this a Power BI Dataflow (Gen1) or Dataflow Gen2 (Fabric)?

What is the exact gateway version installed?

Is the gateway running as a single gateway or gateway cluster?

Did the issue start immediately after a gateway upgrade, or after a recent Fabric/Power BI service update?

Those details will help determine whether this is a gateway registration issue, a cluster issue, or a known Dataflow/Fabric compatibility problem.

Was this reply helpful? Yes No
JJ-27101724-0 19 on at

Like (0)

Report
Copy link

Link copied!
@11manish

This a dataflow in Powerapps from PostgreSQL , type standard V2

Version number 300.318.9

3000.318.9

It is a gateway cluster, with two 2 gateways one has been disabled as it wasnt set up properly

The issue started 1 weeks ago, the dataflow was working fine with no issues. Our other gateaways uat/prod and powerbi reports with are working properly. It just seems to be this dataflow that is failing.

Was this reply helpful? Yes No
Suggested answer

Haque 3,299 on at

Like (1)

Report
Copy link

Link copied!
Hi @JJ-27101724-0,

If version compatiblity is not an issue can you please try these two least possiblities?

1. Sometimes restarting the gateway service and machine works - meaning after upgrading, restart the on-premises data gateway service and, if possible, reboot the gateway server to ensure all components are refreshed.

2. Re-add or reconfigure the data source in the gateway - sometimes removing and re-adding the SQL Server data source in the gateway configuration helps refresh credentials and connection metadata.

Also, we can troubleshoot these two areas:

Check which gateway the failing dataflow is using:

Even though one gateway in the cluster is disabled, the dataflow might still be configured to use that disabled gateway or an outdated gateway instance.

In the Power Platform admin center, verify the dataflow’s configured gateway and ensure it points to the active, updated gateway.

Reassign the dataflow to the active gateway:

Sometimes after disabling a gateway node, the dataflow or data source connection does not automatically switch to the active gateway.

Manually reconfigure the dataflow’s data source to use the enabled gateway.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No