Forum Discussion
Premium_ASWL_Error
Hi,
The reports were working fine for a couple of months, but yesterday I suddenly got this error below.
The reports were not showing in both the Power BI Service and Embedded application. After we re-entered the credentials on the embedded application, this error went. When we re entered credential server name we give without the port number.
What was the reason this issue occurred suddenly?
| 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":"We cannot refresh this dataset because the dataset contains calculated tables or calculated columns based on data from a Single Sign-on (SSO)-enabled Direct Query data source. Please configure the dataset to use an explicit connection with granular access control to access this data source and then try again."}}],"exceptionCulprit":1}}} |
| Cluster URI: | WABI-US-EAST2-redirect.analysis.windows.net |
| Activity ID: | a13987f1-b35a-4c58-b758-96352945dea4 |
Hi Anjan,
Yes, the issue was resolved initially by re-entering the credentials. I wanted to know how the connection was changed, since report was working fine for couple of months. We wanted to know root cause. If Connection has been changed then we did not find any thing in audit logs also regarding the connection change.
Thanks,
Anusha
5 Replies
Hi Anusha__v,
Thank you for reaching out to Microsoft Fabric Community.
Here this error indicates that the semantic model contains calculated tables or calculated columns based on an SSO enabled DirectQuery data source, which is not supported for refresh.
- Since the issue was resolved after re-entering the credentials, it looks like the issue is with the data source connection or authentication was revalidated. If the issue occurs again, please verify that the dataset is configured to use an explicit connection with granular access control instead of SSO.
For reference, follow the below documentation:
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa
Hi @Anusha__v,
We wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi Anjan,
Yes, the issue was resolved initially by re-entering the credentials. I wanted to know how the connection was changed, since report was working fine for couple of months. We wanted to know root cause. If Connection has been changed then we did not find any thing in audit logs also regarding the connection change.
Thanks,
Anusha
Hi Anusha__v,
Thank you for the response and confirming that the issue is resolved. Based on the information provided, we cannot conclude that the connection itself was changed. If no changes are reflected in the audit logs, then there is no indication that the connection configuration was modified.
Since re-entering the credentials resolved the issue, it is more likely that the authentication or connection state had become invalid and was revalidated when the credentials were saved again, rather than the connection type being changed.
Thanks and regards,
Anjan Kumar Chippa
