Forum Discussion

KarenL7's avatar
KarenL7
Icon for Advocate V rankAdvocate V
10 days ago
Solved

Refresh Issues and Take Over Data source settings

Hi We have been having issues with refreshes for the past couple of days with the following error -  We have looked at various posts and noted the way to resolve this was to look at the pri...
Need Help
  • v-achippa's avatar
    v-achippa
    3 days ago

    Hi KarenL7​,

    Thank you for confirming. The right-hand semantic model settings pane is currently in preview. Since the full settings page shows the data sources correctly while the pane shows them as unavailable, this appears to be an inconsistency in the preview interface rather than a gateway or permissions issue.

    For now, please use Open settings to manage and reauthenticate the credentials. If the refresh continues to fail or takeover is repeatedly required, please raise a Microsoft Support ticket with the refresh Activity ID, timestamp and screenshots for further investigation.

    Thanks and regards,
    Anjan Kumar Chippa

ShahRukhSameer's avatar
ShahRukhSameer
Icon for Solution Supplier rankSolution Supplier
9 days ago

Hi KarenL7​,

From what you’ve described, I would first look at the semantic model ownership and the credentials rather than the report itself.

The fact that taking over the semantic model fixes the refresh is a good indication that something has changed around the current owner or the credentials stored for the data source.

A few things I would check:

  • Check who currently owns the semantic model.
  • Go to the semantic model Settings and check the Gateway and cloud connections.
  • Check Data source credentials and re-authenticate if required.
  • If you're using an on-premises gateway, make sure the gateway is online and the data source mapping is still correct.
  • Run a manual refresh and check the refresh history.

One important thing with "Take Over" is that it can clear the existing credentials, so whoever takes ownership needs to configure the data source credentials again.

If this suddenly started happening to several reports without any changes to the reports themselves, I'd look at the authentication/credentials, gateway or source access first.

I wouldn't republish the reports just for this issue, as the problem appears to be at the semantic model/service level rather than the PBIX itself.