Forum Discussion
Power BI Gateway Issue
We have been experiencing the same issue, DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError. We are running a cluster gateway with 3 computers running on the on premise gateway. Issue started on 1-16 out of the blue. It appears when multiple datasets are using the same dataflows but this is occurring on excel files and SharePoint. Reached out to Microsoft to create a ticket... they were not helpful. They just said there is a connection problem. Any advice on how to correct this issue would be helpful.
This is also an intermittent issue for refreshes... cannot determine the exact cause of why sometimes it works and sometimes it doesn't. This is effecting multiple dataflow/dataset refreshes not just one. So, can only assume there is not an issue contained within one model.
Just a follow up from our end. Have been working with MS for a few weeks. Installing agents on our HA gateway servers which are pinging MS sites every 5 seconds and also capturing logs and providing MS with a bunch of logs trying to work out the problem. Will update soon with any resolution.
- andres7772 years agoAdvocate III
Hi Nick,
Did you or Microsoft ever found the fix for the issue or workaround for these TimeOuts?
I'm getting the same error connecting a regular Power BI dashboard to SQL Server...
Thanks
Andres Martinez- OFBReporting2 years agoFrequent Visitor
we started experiencing the same issues today, for no apparent reason. Struggling to get some responses as to why, or even get things back up and running
- NickMac2 years agoFrequent Visitor
Hi all,
Some interesting observations.
As of the 11/6 we now have 4 x 8vpu machines acting as on-premise gateways for our production cluster.
BUT the strangest observation was that from the 1/6 we are no longer seeing the ADO gateway error ?
We didn't implement additional gateways till the 11/6.
Has anyone else noticed that the issue is no longer appearing ? Coincidence with a change in the service ?
We will let this configuration run for the next week to see if we observe any issues and then as an experiment start turning off the additional machines back to the original configuration to see if the problem re-appears.
We need to be conclusive as to whether additional additional gateways and costs to our environment has actually solved the issue.
Will let the community know the outcome.
Nick