Forum Discussion
An error occurred in Power BI Premium backend services
Hi,
I have been encountering this issue ("An error occurred in Power BI Premium backend services") today on a report.
The dataset tied to this report is a composite model and has a Direct Query connection to a remote dataset.
So I have a local and a remote dataset (according to Microsoft semantics in the following documentation: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-composite-models)
The error message was displayed only on visuals using attributes from the remote dataset.
This message being not self explanatory on Power BI Services, I have tried to download the pbix to check on my local machine: no error. Then, I have tried to use DAX Studio to query the local dataset, calling some attributes from the remote dataset using the XMLA endpoint. I was able to get this error message:
07/06/2023 15:20:41
{"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Single sign-on (SSO) credential is not provided which is required to execute the current request. Note that performing a refresh over a dataset with a calculated table or a calculated column which references a Direct Query data source is not supported within the Power BI service."}}]}}}
Détails techniques :
RootActivityId : 0c7dadbb-ecc0-49a1-bdf0-916f743ed4d6
Date (UTC) : 6/7/2023 1:20:40 PM
This error message suggests to get rid of calculated table or calculated columns. Some users in other threads (such as this one) said they were able to fix the issue doing that. However, I think it is not satisfying.
I tried to change the configuration of the dataset on Power BI Services, and found something interesting.
I had someone else from the team taking over the dataset, and configuring the data source credentials (especially for the remote dataset), and it actually worked.
The permissions configured on the remote dataset are the same for the two accounts, so I am stucked in the understanding of this behaviour.
Maybe someone here has an idea?
We had the exact same issue - can't say I understand what caused it, but your workaround with taking over both datasets with another user account and reset the credentials for data sources worked for us.
And we could then reclaim both datasets with our service user account again and now it works just fine.
Thanks!