Forum Discussion
Gateway Issues and Updates
Good morning Community
I tell you that I have been having repeated problems since yesterday with my gateway,
I have several models, Couple of them are updated at the same time and it is happening that some end well and others with error, those that end with error I update manually and there are times when I have to perform this process up to 4 times
The error is as follows:
{"error":{"code":"DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError","pbi.error":{"code":"DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError","parameters":{},"details":[],"exceptionCulprit":1}}}
I had a new version of gateway available and I updated it, restarted the server too and nothing
I hope someone can help me, Have a nice day
Best regards
P.R
Hi Syndicate_Admin ,
Thanks for the update. It's good to hear that setting up two gateways improved things. Sometimes, intermittent failures happen when the load is high or the models are large. To make refreshes more stable, you can ensure both gateways are in a cluster for load balancing, space out your dataset refresh schedules so they don’t all run at the same time, and use incremental refresh on big datasets so only new or changed data gets updated, which reduces strain. You can also automate dataset refreshes for more control: for example, by using the Power BI REST API to trigger a refresh, using Power Automate's "Refresh a dataset" action to schedule or run refreshes based on events, or using scripts in Python or PowerShell to call the API and handle retries automatically. Additionally, keep an eye on gateway logs and dataset refresh history to spot any failures, and consider breaking very large datasets or heavy transformations into smaller parts if needed. This setup helps manage refresh timing and load better, reduces failures, and works well with your existing pipelines.
Refer this Documentation Links:
https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/refresh-dataset
https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overviewhttps://learn.microsoft.com/en-us/power-bi/connect-data/refresh-data
7 Replies
Hi Syndicate_Admin ,
Try below things.
1. Reduce Refresh Concurrency,
In Power BI Service, Manage Gateway → Settings → Limit the number of concurrent queries. Set to: 1 or 2 for small servers and 3–4 for high capacity servers.
2. Avoid scheduling multiple huge models at the exact same time.This spreads gateway and DB load.
3. Modify your connection string in Power Bi CommandTimeout=1200;ConnectionTimeout=60 Or in Gateway (if using SQL):
Advanced settings → Command timeout → 1200 seconds.
4. Make sure the gateway has unrestricted outbound traffic to Microsoft Fabric endpoints. Disable
SSL interception, DPI ,proxy rewriting and TLS inspection.
5. Gateway should have 16 GB RAM minimum and 8 vCPU recommended. If using the same VM for other services → isolate the gateway.
6. Restart gateway service not just server.
services.msc → On-premises data gateway service → Restart.
If my response as resolved your issue please mark it as solution and give kudos.
Good day, Thank you very much for your Answer
Consultation
Is there a possibility of having more than one GateWay on 2 servers and that my models point to GateWay 1 and others to GateWay 2?.
I'm trying not to leave them all at the same time, but I have about 15 models and having an update every 30 mins is delayed a lot, do you know any other way to update whenever I want automatically?
I remain attentive to your answer
Best regards
P.RHi Syndicate_Admin ,
You can definitely run multiple Gateways on two different servers. There are two ways to set this up:
Gateway Cluster - Install Gateway A on Server 1 and Gateway B on Server 2, then add both to the same cluster. Power BI will automatically distribute refresh load across the two servers, which helps a lot when you're dealing with 15 models refreshing frequently.
Separate Gateways - If you prefer, you can keep the gateways independent. In each dataset's Settings - Gateway Connection, simply choose whether that model should use Gateway 1 or Gateway 2. This gives you full control over which models go where.
Regarding refresh timings: when many datasets refresh every 30 minutes, the gateway can easily get overloaded. Try staggering the refresh times slightly or consider using Incremental Refresh if your model supports it. If you want a 'refresh whenever I need it' option, you can trigger refreshes using the Power BI REST API, Power Automate, or a small automation script.
Hi Syndicate_Admin ,
I would also take a moment to thank Anonymous , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
