Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

0

Schedule Refresh failed (Premium_ASWL_Error)

Starting last week, I have had schedule refreshes failing with this message:

  • Data source error{"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Cloud data source refresh is not allowed in gateway setting."}}],"exceptionCulprit":1}}} Table: MyTableName.

The table(s) the error is relating to come from Sharepoint folders. Currently it is happening in 2 different reports.

 

The schedule refresh had been working fine previously for months. I did not make any change to the dataset recently.

 

Status: Delivered
Comments
Anonymous
Not applicable

Hi @Armando_AD ,

 

This is the reason why customer is uanble to refresh the dataset or vew the report built on this dataset.

Possible mitigations are below

1. Republish the pbix file (which seems already done but not work)

2. Convert storage mode of dataset manually with guidance back and forth. (Large model storage format: "Disabled -> Enabled -> Disabled" or "Enabled -> Disabled -> Disabled" depends on the inital status)

https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-large-models#enable-large-data...

 

If both mitigations doesn't work, then it's inevitable that customer needs to publish a brandnew dataset by either publish with a new name or delete the problematic dataset first then publish again.

 

Best Regards,
Community Support Team _ Caitlyn

Armando_AD
Frequent Visitor

Thanks for your reply @Anonymous 

I tried all of the above with no success. I published to a different workspace under a different name and the result was the same error.

Something that does not make sense to me is that I am not using Premium workspaces for any of the Datasets

Armando_AD
Frequent Visitor

After further testing, I realized that the tables causing those errors contain either merged or appended queries from SQL and Sharpoint. I tested by joining in the data model and it is working fine.

 

@Anonymous  Is this error related to other issues I've seen posted about Sharepoint refresh errors? Is a solution coming or I better change the model to join with DAX?

DataMindedLLC
New Member

@Armando_AD I had this same error and I was able to resolve it by having my sharepoint connection run through my on premise data gateway. Once the two connections (one to SQL Database and one to Sharepoint Online using OAuth2) were running through the same gateway I was able to refresh the dataset via the service. 

 

This does seem to be a result of a query from SQL that had merged/appended data from an excel file hosted in SharePoint Online. 

I had to use append in my situation so the data would look like one dataset to keep it simple for the end user.