Dataset Incremental Refresh failing due to "metadata change"

[Anonymous]

Hi,

We've got a really strange issue with a dataset that has incremental refresh enabled on a couple of tables.

Since a few days the incremental refresh stops working, more specifically, after midnight.
If I republish the dataset incremental refresh works throughout the day, but after midnight it breaks again... 😐

I did check our PBI gateway servers, but there are no entries in the error logs.

So it looks like an issue on PBI service, but I have no clue what...

Following rather general error is thrown:

Data source error:	Metadata change of current operation cannot be resolved, please check the command or try again later.
Cluster URI:	WABI-NORTH-EUROPE-F-PRIMARY-redirect.analysis.windows.net
Activity ID:	b0b55682-7db6-4c8c-ac0e-61cc5f13f5fe
Request ID:	1adeb0e6-fda8-492e-bf99-feafb905f1ff
Time:	2021-03-19 00:04:17Z

Any help is much appreciated!

Kind Regards,

Thomas

[v-lili6-msft]

hi

If the dataset is in Premium workspace or Shared workspace?

try to publish the report to another workspace to have a test.

Regards,

Lin

[Anonymous]

Hi Lin,

It's in a premium workspace.

Ok, I'll try to publish it to another premium workspace to see how it goes.

Kind Regards,

Thomas

[d2shah]

Hi Thomas, 

I am encountering the same issue. 

The issue seems to be isolated to Power Bi Premium, as the refresh works fine in shared capacity (PRO). 

I have tested using multiple different workspaces with Premium Gen 1, Premium Gen 2, and Premium Per User Capacity. I have also tried testing it with different VM, databases, gateways, and tenants all with the same result. 

I am working with Microsoft support to resolve the issue. I will let you know if I get a solution from them.

Regards,

Dhyan

[Anonymous]

Hi Dhyan,

That would be great, thank you!

Also good to know that I'm not alone with this strange behaviour 🙂

@v-lili6-msft 

I did test an upload to a brand new workspace, but same error after midnight 😕
As 

Regards,

Thomas

[s2ramana]

Thomas,

I suggest that you also report it to Microsoft Support as well to put pressure on their product team to properly investigate. We are waiting on the Microsoft Product Team to get back to us on the issue and they have not yet responded. This appears to be a serious issue with Premium workspaces in general and Microsoft appears to be slow to recognize it as such.

Regards,

Siva

[Anonymous]

Hi Siva,

I've created a support ticket, case 2103240050000207 😉

Kind Regards,

Thomas

[d2shah]

Hi Thomas, 

Microsoft got back to me and acknowledged it's a bug on the system that they are working to fix.

The fix should be deployed around April 10th. 

The bug seems to be related to using a custom connector with a Premium workspace.

Are you using a custom connector? 

Regards,

Dhyan

[Anonymous]

Hi Dhyan,

Thanks for the update! I'm indeed using custom connectors in a Premium workspace.

Yesterday I made a copy in a non-Premium workspace and, indeed, I didn't get the issue 🙂

Kind Regards,

Thomas

[Anonymous]

Hi All,

I can confirm that the issue is resolved since 10/04

Kind Regards,

Thomas

[d2shah]

Hi Thomas, 

It's resolved on our side as well. 

Regards,

Dhyan