Forum Discussion
Unable to edit Data Source Credentials after publishing - Azure SQL
I've changed a Dataset and now I'm having problems refreshing the data. I believe the issue is related to Data Source Credentials.
I've changed one of the data sources in the dataset from a Sharepoint List to an Azure SQL database. I've connected to the Azure SQL DB, modifed all the reports in Power BI Desktop and they all work as expected. I've published the report to Power BI and now I can't refresh that data source.
I've read on here that when you publish a report from Power BI Desktop you need to re-ented the Data Source Credentials. I have and the sign in seems to be successful but they don't appear to be saved. When I try to manually refresh the data, it fails and when I go back to Data Source Credentials I see the following message.
When I try to Edit Credentials it always appears to have set back to Windows authentication. I change it to Basic, add the SQL user and password and Sign in.
I get a little Sign In Succesful message in the top right corner of the screen but when I try to refresh, the refresh fails.
I'm not that experienced with Azure SQL but I could really do with some help. "Allow Access to Azure Services" is turned on for the DB. Thanks in advance.
8 Replies
Perhaps go back to your Desktop file and click File | Options and settings | Data source settings.
Double-click on the data source and then edit the credentials and re-publish.
Thanks but that doesn't do anything. I've edited the data sources (again) before I publish the report and I've checked they refresh OK locally. I then publish the report and the dataset then will not refresh.
What is odd is that data IS refreshing. Changes to the source data are visible in the reports. Is there anywhere to get a more detailed breakdown of what is failing in the data refresh?
Hi iainshaw,
Have you tried windows authentication? Please also check if gateway has been updated to the lastest version. If the issue still occurs, can you post some fiddler trace for further analysis?
Regards,
Jimmy Tao
Both data sources in the dataset are online (an Excel file in OneDrive and an Azure SQL DB) so I don't think it is using the Gateway. I can only use SQL user and pass for the Azure SQL DB. I am happy to post more details.
Last refresh failed: Mon Jul 30 2018 11:21:34 GMT+0100 (British Summer Time) The last refresh attempt failed because of an internal service error.Hide details Cluster URI: WABI-UK-SOUTH-redirect.analysis.windows.net Activity ID: 9bfdb906-b4c6-98ec-efb4-542a7747f55a Request ID: bae62160-0f93-bf2e-db3e-b946c080a2fb Time: 2018-07-30 10:21:34Z
What is odd is that the data is refreshing. I make changes to both of the source data and I can see the changes in both in my reports after the data refresh. Is it possible to have a partial refresh?
I've changed a Dataset and now I'm having problems refreshing the data. I believe the issue is related to Data Source Credentials but I can't seem to edit the credentials successfully to make it work.
I've changed one of the data sources in the dataset from a Sharepoint List to an Azure SQL database. I've connected to the Azure SQL DB, modifed all the reports in Power BI Desktop and they all work as expected. I've published the report to Power BI and now I can't refresh that data source.
I've read on here that when you publish a report from Power BI Desktop you need to re-ented the Data Source Credentials. I have and the sign in seems to be successful but they don't appear to be saved. When I try to manually refresh the data, it fails and when I go back to Data Source Crendtials I see the following message.
When I try to Edit Credentials it always appears to have set back to Windows authentication. I change it to Basic, add the SQL user and password and Sign in.
I get a little Sign In Succesful message in the top right corner of the screen but when I try to refresh, the refresh fails.
I'm not that experienced with Azure SQL but I could really do with some help. "Allow Access to Azure Services" is turned on for the DB. Thanks in advance.
