Data Refresh error: "DM_GWPipeline_Gateway_CanceledError"

[sandy_ew]

I've been experiencing an intermittent data refresh issue with the Power Bi Service semantic data model with the following error code: "DM_GWPipeline_Gateway_CanceledError".  

No change has occurred to the data model or underlying Azure Sql database prior to this issue starting to appear intermittently. 

Things I've tried:

- checking that the data connector is set to "Organizational" level of access

- updating the data connector to see if that reset things

- updating the processing power of the back-end Azure SQL database

Any help is appreciated.  It's only been happening recently but has been ticking along happily for over 6 months prior to this.

Thanks in advance.

[kcwilsonii1]

I had similar issues and updated the Gateway software. 

The issue seemed unrelated though, turned out to be tcp/ip traffic rules causing the 

problem. The vendor handling our internet connection had updated the traffic rules which started a variety of issues at work including the Gatway refreshes crashing repeatedly.

In the end the vendor had to roll back the updates, but also had to update firmware on the hardware as they

were one version behind. They then applied the rules in batches. Everything is fine now.

Make sure you don't have to tcp/ip issues, hardware is updated and check router configurations for your Lan to Wan connections

[foresightbi]

@kcwilsonii1 ,

What TCP/IP traffic rules in particular were the issue for you?  

[kcwilsonii1]

I do not know exactly which one but they did have to make adjustments for the Gateway traffic to and from powerbi.

I still belive their biggest problem was that they had not updated the wan device to the latest software and firmware version

[foresightbi]

Interesting.  

Well we've tested with isolating our machines in the policy to be exempt from rules period to see if that would help but the problem remains for us.  Our configuration on the networking side hasn't changed in YEARS for these machines and we even did the february upgrade in early March.  This configuration has been fine for us until just last week.

It's hard to rationalize this being a configuration issue on the client side.  My opinion is that this is an MS issue that's being resolved by workarounds on the client side.

[ConfusedPBIUser]

Our organization started experiencing this issue last week and we are seeing around 100 failures daily. Whenever we manually re-trigger the refreshes, they always succeed. It is only scheduled refreshes that (intermittently) have this problem.   

Anyone have any solutions? 

[awright19]

We just installed the latest gateway in the hopes that it will resolve the issue. Will keep you updated.

FYI, for us it has been both scheduled refreshes as well as some manual refreshes.

[ConfusedPBIUser]

We updated to the latest version last week and saw no difference. The Microsoft engineer also told us beforehand that it was unlikely to fix the issue since the February gateway version only had minor updates. He said the March version should have more changes and might resolve the issue. 

[GilbertQ]

Hi @ConfusedPBIUser 

Is it happening with a Gateway or not?

If it is a Gateway please make sure it is running the latest version of the Gateway software?

[ConfusedPBIUser]

It is via the on-premise data gateways and it is on the latest version (February 2025).

[awright19]

FYI, there is a newer update from March 12. We just installed it and so far so good. It's only been since last night, so I'm not calling it fixed yet, but we'll see.

[ConfusedPBIUser]

That's the one we are already on, 3000.258.6 (February 2025). Unfortunately no dice for us so far. 

[two_sandy]

[same message as my other issue]

I have again stopped experiencing this issue but it's the result of nothing I've done my end.  

Initially I had heaps of errors occurring for the automated data refreshes, but not when I manually refreshed my data model (similar to how you describe your issue).  The errors stopped some time after I raised this case (under another profile).  They then occurred a few times again about a fortnight ago but I've not had one happen since then.  

I wish I could tell you what the issue was / is.   

[awright19]

To keep everyone updated...our Microsoft ticket has been escalated and they acknowledge that other companies are seeing the same issue.

We were told to increase our disk space, to see if that resolved the issue. We have done so twice now, and are still getting the issue. Less volume of failures, but still there.

[vinny1986]

We have increase memory on the server where our gateway is too but it didn't resolve fully. Now they are saying we should roll back to October gateway version before the problem started.

[andy808]

Just following up here, we are still experiencing this error multiple times daily. Have you found success?

[ConfusedPBIUser]

Were you able to resolve this issue? 

[two_sandy]

I have again stopped experiencing this issue but it's the result of nothing I've done my end.  

Initially I had heaps of errors occurring for the automated data refreshes, but not when I manually refreshed my data model (similar to how you describe your issue).  The errors stopped some time after I raised this case (under another profile).  They then occurred a few times again about a fortnight ago but I've not had one happen since then.  

I wish I could tell you what the issue was / is.   

[awright19]

We're still dealing with it as well. The frequency has decreased, but we had another one this morning. Our ticket is still open with Microsoft.

[vinny1986]

Microsoft support told us to roll back to September version of the datagateway. We installed it and it works so far.

[awright19]

Did they give you any indication that they were fixing it for future releases? Or are they saying you should just stay with the September release indefinitely?