Forum Discussion
Assistance Required for Power BI Dashboard Refresh Configuration in On-Premises Environment
I have published the dashboard to our on-premises environment using the Save As option from Power BI Desktop. However, I am facing challenges while configuring the scheduled refresh for the dashboard.
During the refresh setup, the system prompts for data source credentials. Even after entering the required credentials, they are not being accepted, which is preventing me from completing the scheduled refresh configuration.
Could someone please assist me with:
- Configuring scheduled refresh for an on-premises Power BI dashboard.
- Resolving the PostgreSQL data source credential authentication issue.
- Verifying if any additional gateway, permission, or configuration settings are required.
Your guidance and support would be greatly appreciated.
Hi,
I've run into this before, usually comes down to the PostgreSQL driver not being installed on the actual server/gateway machine, not just your local PC. Worth checking that first.
A few quick things I'd check:
Confirm the auth type is set to Database/Basic, not Windows auth, that trips people up a lot with Postgres.
If you're using a Gateway, make sure the driver's installed there too and the data source matches your PBIX connection details exactly.
Try logging in with the same credentials via pgAdmin or DBeaver from that same server, if that fails too, it's not a Power BI issue at all, it's network/auth on the Postgres side.
Also check pg_hba.conf allows connections from that server's IP, I've seen "invalid credentials" errors that were actually just the Postgres server blocking the connection outright.
Let me know if this is Report Server or Gateway based and I can narrow it down further.
💡 Helpful? Give a Kudos 👍 — keep the community growing.
✅ Solved your issue? Mark this as the Accepted Solution ✔️
Best regards,
Prince Singh | Data Science & Microsoft Fabric Enthusiast
4 Replies
- Kagiyama_yutaka
Continued Contributor
On Power BI Report Server, scheduled refresh works only for Import reports and uses the PostgreSQL Database/Basic credentials stored in Manage → Data Sources. PBIRS connects directly, so no gateway is involved.
For PostgreSQL, the Report Server must have a supported PostgreSQL provider installed, matching the PBIRS Desktop version. PBIRS works with ODBC or Npgsql, depending on the build.
If credentials are rejected during refresh setup, the usual cause is that the PBIRS server is missing the correct PostgreSQL provider, even if Desktop can connect.
- Prince0011
Solution Sage
Hi,
I've run into this before, usually comes down to the PostgreSQL driver not being installed on the actual server/gateway machine, not just your local PC. Worth checking that first.
A few quick things I'd check:
Confirm the auth type is set to Database/Basic, not Windows auth, that trips people up a lot with Postgres.
If you're using a Gateway, make sure the driver's installed there too and the data source matches your PBIX connection details exactly.
Try logging in with the same credentials via pgAdmin or DBeaver from that same server, if that fails too, it's not a Power BI issue at all, it's network/auth on the Postgres side.
Also check pg_hba.conf allows connections from that server's IP, I've seen "invalid credentials" errors that were actually just the Postgres server blocking the connection outright.
Let me know if this is Report Server or Gateway based and I can narrow it down further.
💡 Helpful? Give a Kudos 👍 — keep the community growing.
✅ Solved your issue? Mark this as the Accepted Solution ✔️
Best regards,
Prince Singh | Data Science & Microsoft Fabric Enthusiast - v-csrikanth
Community Support
Hi Raj2108se
We would like to inquire whether have you got the chance to check the solutions provided by Kagiyama_yutaka Prince0011 in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community. - v-csrikanth
Hi Raj2108se
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Thank you.
