Power BI Service refresh error

[rdavitt]

Hi Team, I am experiencing an issue with a semantic model no longer refreshing in Service, it has previously refreshed and been no issues with the Calculated Table in the dataset. Now I am getting this error:

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.

I am unsure how to fix this as my dataset uses all tables in DirectQuery and the calculated table is an Import, The inital refresh failure message was actually to do with authentication.

DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS50057: The user account is disabled."

I am unsure if the error means its related to the authentication or the calculated table, the refresh itself works fine in Desktop - it's no longer doing the scheduled refresh or manual refresh in Service.

I have attempted to re-enter the authentication and retry but still getting the top error! Can anyone advise? Thanks

[Anonymous]

Hi @rdavitt ,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you.

Regards,
Pallavi G.

[Anonymous]

Hi @rdavitt ,
Could you please confirm if the issue has been resolved after raising a support ticket? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.

[rdavitt]

Hi @Anonymous,

Thanks for coming back with a proposed solution. I have tried all the above mentioned things (some of them multiple times and still recieveing the same error message. How do I configure the dataset to use an explicit connection with granular access control to access this data source and then try again? could that be the issue?

Thanks

[Anonymous · Accepted solution]

Hi @rdavitt  ,
Please try to republish the dataset from Power BI desktop to Power BI Service and check step by step again if still face the same issue then please consider raising a support ticket for further assistance.

To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Thank you for being a part of Microsoft Fabric Community Forum!

[Anonymous]

Hi @rdavitt ,

Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you are encountering.

Providing few points which might assist you in resolving the issue:

1.Try to reconfigure the authentication for the data source.To do, go to the dataset settings in Power BI Service, select the data source, and update the credentials.
2.Power BI Desktop settings,click Edit Permission to modify the Privacy Level. Sometimes Privacy Level can also affect the data source connection error.
3.Check gateway is properly configured and up to date.
after all changes, try to republish the dataset from Power BI Desktop to Power BI Service.

If still facing difficulty in resolving the issue, please feel free to reachout.

If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.