Forum Discussion
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 privacy settings in the report and then republish.
The way to resolve was for someone else (also admin) to "Take Over" the dataset settings and then refresh the report.
Please note that we also have had issues with the right hand pane with pops out when the "Schedule Refresh" button is selected, so we can take over the dataset settings from there - Despite being successful
"Data Source Credentials" are greyed out.
If we "Open Settings" pane
data Source credentials are available -
To Confirm -
We have not had any changes in any of the reports or datasources within the service. The refresh has been constant and not had this issue.
The owner of the dataset was trying to refresh the report was unable to and the refresh failed with the error message.
Please note that the owner of the dataset has admin rights
I am wondering what has changed for us to suddenly encounter this issue? We are concerned this is going to keep happening.
Thanks
Karen
5 Replies
- ShahRukhSameer
Skilled Sharer
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.
- DaniyalKhaleel1
Helper II
Most likely, this is a Power BI Service ownership/credential management issue, not a change in your reports or data sources.
Admin rights ≠ semantic model ownership for all settings.
Data Source Credentials greyed out suggests an ownership/connection context issue.
Take Over changes the semantic model owner and can restore access to credentials/settings.
Since multiple reports were working previously with no changes, a Power BI Service/backend change or credential/connection issue is possible.
Take Over is a workaround, not an ideal permanent solution
- AnalyticPulse
Solution Sage
hi KarenL7
a gateway-related refresh problem can occur even when the PBIX and Power Query logic have not changed.
please verify the complete connection path:
Power BI Service > Semantic Model > Gateway Connection > Gateway Data Source > Credentials > Actual Data Source
Check Gateway and cloud connections
Go to: Workspace > Semantic model > Settings > Gateway and cloud connections
Confirm that the expected gateway is shown and that its status is Online.
My Work:
Analytic Pulse Blog
Docynx Productivity Tools
Generate Realistic Sample Data Instantly onlineDashboard: Explore the live demo and full design insights on Docynx
- KarenL7
Advocate V
Thanks for your replies, they are helpful
Just to confirm -
- Check who currently owns the semantic model.
- can confirm the the admin is the owner
- Go to the semantic model Settings and check the Gateway and cloud connections
- Gateway and cloud connections are fine - these can be checked but the data source cannot.
- Check Data source credentials and re-authenticate if required.
- Unable to do this as it greyed out and unavailable.
- If you're using an on-premises gateway, make sure the gateway is online and the data source mapping is still correct.
- Gateway is online and as the report has not changed the data source is correct as it has been refreshing for a while - and permissions have been granted to the sources.
- Run a manual refresh and check the refresh history.
- This only worked with the following solutions -
Solutions so far -
- Although not ideal the other admin had to take over the settings so we can resolve it. The datasource credentials were available again in some cases and they had to reauthenticate against the source and refresh was successful
- One instance we redeployed the report to resolve this.
As we have not had this issue before, we will keep an eye on it.
Concerned about the settings pane being different from the pop out screen though? As I can see the credentials all ok in one screen but not the other - not sure if anyone else has noticed this?
Thanks
Karen
- Check who currently owns the semantic model.
- tayloramy
Super User
Hi KarenL7,
This error has nothing to do with credentials or ownership.It has to do with the privacy level of the connections, currently in your model it is set to none.
Set each connection to Organizational and then Power BI will be able to combine data.
See the docs for more info:https://learn.microsoft.com/en-us/power-query/privacy-levels