Forum Discussion
Scheduled refresh fails on Service connecting to PostGreSQL
Hi all,
I have gone through similar issues solutions provided here but don't seem to work. However, same as others, the refresh owrks fine in Power BI Desktop but one published, I get a credential error when refreshing my semantic from Service. Here is the error that I receive:
Something went wrong
Scheduled refresh has been disabled.
- Data source errorScheduled refresh is disabled because at least one data source is missing credentials. To start the refresh again, go to this dataset's settings page and enter credentials for all data sources. Then reactivate scheduled refresh.
Note: I have inserted the credentials (UID/PWD...) but getting the same result
Thanks in advance
Hi ekodami,
The point raised by GilbertQ is important to check, as the connectivity path significantly affects how credentials are processed in the Service.
Additionally, you might want to review these common areas that could cause this issue:
Reconfigure credentials
Clear the current credentials in the Service and re-enter them. Sometimes old credentials can become inconsistent.Authentication method alignment
Make sure the authentication type in Power BI Service matches what was used in Desktop. Even small differences can cause errors.Connection details consistency
Verify that the server name, database name, and port are exactly the same as those used during development. Using an IP address in one place and a hostname in another can cause problems.Republish the dataset
Republishing the dataset with a different name can sometimes resolve hidden configuration or metadata issues.PostgreSQL access configuration
Check that your PostgreSQL setup allows external connections and that there are no restrictions, such as SSL requirements or role limitations, blocking authentication from the Service.
Thank you.
3 Replies
Hi Gilbert, thanks for your response and apologies for the delay in giving a feedback. I was actually waiting after my internal Power BI team input prior to get back with the correct answer. Yes, of course we use an on-prime gateway and I didn't have a connection set for our Power BI Service to go through and get data from PostGreSQL db tables. The gateway is being configured and hopefully everything goes on from there.
Thanks again!
Hi ekodami,
The point raised by GilbertQ is important to check, as the connectivity path significantly affects how credentials are processed in the Service.
Additionally, you might want to review these common areas that could cause this issue:
Reconfigure credentials
Clear the current credentials in the Service and re-enter them. Sometimes old credentials can become inconsistent.Authentication method alignment
Make sure the authentication type in Power BI Service matches what was used in Desktop. Even small differences can cause errors.Connection details consistency
Verify that the server name, database name, and port are exactly the same as those used during development. Using an IP address in one place and a hostname in another can cause problems.Republish the dataset
Republishing the dataset with a different name can sometimes resolve hidden configuration or metadata issues.PostgreSQL access configuration
Check that your PostgreSQL setup allows external connections and that there are no restrictions, such as SSL requirements or role limitations, blocking authentication from the Service.
Thank you.
