Forum Discussion
Power BI Gateway Issue
Has anyone received resolution on this issue? We have noticed that reducing the number of servers on the cluster has actually improved the performance of the refreshes. We went from the largest dataset refreshes failing almost every time based on this error message…
DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError
To now only failing sporadically. Would like to resolve the issue permanently. Does anyone else have any other suggestions on how to get this to work?
This is the exact opposite of what MS has recommened. Can you please share your cluster configurations and whether these are sitting in the Azure cloud as onprem gateways or are they really on prem in your data center.
Nick
The gateway configuration we have is different then yours. We have 3 computers setup on the cluster, they are all on-premise running the on-premise data gateway. The only reason I said server is because that was the terminology that Microsoft uses for gateway machines.
I tested this about a month ago… thought that it was running better on one computer. Then pushed Microsoft for a resolution for the cluster issue. They must be a on a 3 day SLA for responses. Only getting a half response on the issue from them once every 3 days. Had a call with them… they needed to get the log files. Which we are unable to retrieve from the on premise gateway logs. The export log files after selecting the date does not work. Still trying to understand what log files they even need. Since this is a cluster the log files will need to be retrieved from all the cluster machines.
The customer service engineer seemed to think there was an issue with one-file causing the connection timeout issue. Not sure that one file would cause all the other dataflows and datasets to fail, with all different connections in them.
We have also received error messages below…
DM_GWPipeline_Client_AsyncOperationExpired
When we receive the above error the next refresh tends to be the connection timeout error.
Your data gateway is offline or could not be reached.
We have received this message but it is not very seldom.
These all appear to be some type of network issue.
We also went through the network connection issue. Pushed this to the network team… they said they didn’t see anything wrong with the network. Ran a ping test and didn’t see any major failures. All the gateways are in the same location. There are other users using Power BI at our company in different locations on different gateways with no problems. So, I think it might be an individual computer/network problem on the cluster but haven’t flushed it all out yet. Turned off all computers on the cluster except for one… running tests on each one individually. It is running on some but not all machines. Trying to see if there is some kind of setup issue with one machine.
This link may help you. It appears that when there are multiple computers configured on the cluster the datasets are pushed to all cores on the gateway… If there is a failure on one gateway then the entire refresh will fail. This seems to be why we are having the failures based on one machine in the cluster causing issues for entire refresh. Would be nice if Microsoft would create a tool to monitor the cluster usage and identify which cluster computer is causing failures. This appears to be the case with the gateway cluster I am experiencing.
Working with Power BI Gateway logs - Microsoft Fabric Community
Would like to get resolution from Microsoft but that doesn’t appear to be the case. Since the ticket has been open with Microsoft for about 1.5 months now.