Forum Discussion
Intermittent On-Prem refresh failure: "The credentials provided for the Web source are invalid"
Hi Anonymous
Given the intermittent nature of the failure and the fact that it only occurs on the On-Prem server, here are a few steps and considerations that might help resolve or isolate the issue:
-
Verify Gateway Configuration: Ensure that the On-Premises Data Gateway is correctly configured and running. The gateway acts as a bridge for data refreshes from on-premises sources to the cloud. For detailed steps on setting up and configuring the gateway, please refer to the official documentation: Tutorial: Connect to on-premises data in SQL Server - Power BI | Microsoft Learn
-
Check for Gateway Updates: Make sure that your On-Premises Data Gateway is up to date. Outdated gateways might have issues with certain types of connections or authentication methods.
-
Review API Rate Limits: Although you mentioned that the endpoint seems stable when tested with Postman or Python, intermittent failures on the server could still be related to API rate limits or throttling. It's possible that the server's refresh attempts are being rate-limited.
-
Investigate Network Issues: Since the issue is specific to the server environment, it might be worthwhile to investigate any network-related issues that could be affecting the connection to the API endpoint. This includes checking firewall settings, DNS resolution, or any network security appliances that might be interfering with the connection.
Best Regards,
Jayleny
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
thanks for the tips, I do appreciate them. suggestions #1-2 don't apply as the dashboard is hosted on the on-prem server and does not use a cloud gateway. RE #3, the number of refreshes are very low, approximately less than 10 per day. I can run this many with postman and not hit such a limit. If #4 then it would have to be on the server side since this is the only place it is reproduced.
Unfortunately this still leaves this issue unsolved. I may also add that there other dashboards that access this same endpoint which fail far less frequently than this particular dashboard. I'm thinking perhaps there is something in the data model which could exacerbate this symptom. Investigation is still open.