Forum Discussion
Your data source can't be refreshed because the credentials are invalid
Hello,
I've been using Power Bi for almost a year now and I created several reports. I'm using data from a PostgreSQL database and a few simple Excel files. I've uploaded most of these reports to Power BI service and scheduled refreshes on them and shared the reports with my colleagues. Three weeks ago a I noticed that some of the reports were not refreshing anymore but some still were. All the reports have the same error message though, see image below
It worked flawless for almost a year but since three weeks I get these error message but noting changed. Obviously I double checked my creddentials and they are correct. I tried to update the npgsql but that is also not working. I can import data from the PostgreSQL server to Power Bi Desktop manually. The problem seems to be between Power Bi desktop and Power Bi service.
Does anyone know what the problem is and how to resolve it.
Hi CCChrisvdlaken ,
There are several points you may considerate:
1.Ensure that you've added one or more data sources of your dataset to the gateway, as described in Add a data source.
2.Verify that you have the correct username and password. Also, verify that those credentials can successfully connect to the data source. Make sure the account that's being used matches the authentication method.
3.Your data source credential may expire, so try to update the credential and republish the report. In Power BI, go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source.
4.If your dataset not only contains cloud data source but also the on premise data source, then it needs to use the gateway and configure schedule refresh, see more: :On-premises data gateway , Configure scheduled refresh .
Note that you also need to select Allow user's cloud data sources to refresh through this gateway cluster option Under Gateway Cluster Settings. See: Merge or append on-premises and cloud data sources.
5.Please make sure the gateway is online, and try to upgrade the gateway to latest version. You might also need to upgrade the Power BI Desktop to the latest version 2.75.5649.961 . Download the pbix file from Power BI Service, then reopen in Power BI Desktop and republish to Power BI Service. See the similar case.
6.Please set schedule refresh for different datasets at different times, make sure that you don't schedule more than max parallel refreshes for the different nodes in these capacities. Also we suggest that you first disable all refreshes on all capacities. Then slowly enable the refreshes one by one. Make sure refreshes are staggered apart (e.g. 1 hour apart), and that no more than max concurrent refreshes happen at overlapping time periods.
7.Power BI Pro or Power BI Free supports uploading Power BI Desktop (.PBIX) files that are up to 1 GB in size. Power BI Premium supports uploading Power BI Desktop (.PBIX) files that are up to 10 GB in size. If you need to upload PBIX file that is larger than 10 GB, consider to move data from your source to SQL Server, Oracle or SSAS, then use DirectQuery/Live connection.
You may resolve the issue via the troubleshooting link :https://docs.microsoft.com/en-us/power-bi/refresh-troubleshooting-refresh-scenarios .
Best Regards,
Amy
Community Support Team _ Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
v-xicaiCommunity Support
Hi CCChrisvdlaken ,
There are several points you may considerate:
1.Ensure that you've added one or more data sources of your dataset to the gateway, as described in Add a data source.
2.Verify that you have the correct username and password. Also, verify that those credentials can successfully connect to the data source. Make sure the account that's being used matches the authentication method.
3.Your data source credential may expire, so try to update the credential and republish the report. In Power BI, go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source.
4.If your dataset not only contains cloud data source but also the on premise data source, then it needs to use the gateway and configure schedule refresh, see more: :On-premises data gateway , Configure scheduled refresh .
Note that you also need to select Allow user's cloud data sources to refresh through this gateway cluster option Under Gateway Cluster Settings. See: Merge or append on-premises and cloud data sources.
5.Please make sure the gateway is online, and try to upgrade the gateway to latest version. You might also need to upgrade the Power BI Desktop to the latest version 2.75.5649.961 . Download the pbix file from Power BI Service, then reopen in Power BI Desktop and republish to Power BI Service. See the similar case.
6.Please set schedule refresh for different datasets at different times, make sure that you don't schedule more than max parallel refreshes for the different nodes in these capacities. Also we suggest that you first disable all refreshes on all capacities. Then slowly enable the refreshes one by one. Make sure refreshes are staggered apart (e.g. 1 hour apart), and that no more than max concurrent refreshes happen at overlapping time periods.
7.Power BI Pro or Power BI Free supports uploading Power BI Desktop (.PBIX) files that are up to 1 GB in size. Power BI Premium supports uploading Power BI Desktop (.PBIX) files that are up to 10 GB in size. If you need to upload PBIX file that is larger than 10 GB, consider to move data from your source to SQL Server, Oracle or SSAS, then use DirectQuery/Live connection.
You may resolve the issue via the troubleshooting link :https://docs.microsoft.com/en-us/power-bi/refresh-troubleshooting-refresh-scenarios .
Best Regards,
Amy
Community Support Team _ Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
v-xicaithank you for your comprehensive reply. I tried configuring the on-premise gateway and that worked for me! Finally a solution after three weeks.
