Meaning of DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError

[dbeavon3]

Can someone give an english translation for the error "DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError"?

It is happening today in all of our datasets.

Perhaps we should submit an "idea" about this error message to the product team ?  The "idea" is that error messages should be human-readable (preferably in English).  Error messages should not be reported as one-word codes that nobody understands.  In most software programs, error messages are supposed to convey some meaning to a user.  Otherwise they might as well just say "something bad happened" and leave it at that. 

Is it possible that this message is not intended for people to read, but for an Artificial Intelligence?  

[dbeavon3]

For the sake of those wanting to avoid calling support, Microsoft's primary recommendations will be :

• Reboot gateway servers
• Update gateway software.
  
  
  If you truly want to save time, you should probably do these before asking Microsoft for help.  This issue comes up regularly, and life is too short to open a ton of tickets about the same thing.

[dbeavon3]

It happened again today.  The solution is simply to reboot the gateway servers.

In summary, you can interpret the error DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError to mean the following:

Your Power BI gateways are exhausted and confused.  They need a short vacation but, rest assured, they will get back to work again after they are rebooted.  Please do not open a support ticket with Mindtree until after you have rebooted the gateways.  While you are at it reboot your own laptop as well.  If things aren't back to normal at that point, then you should also contact Mindtree tech support and ask them to reboot Azure.  

Hopefully that is clear.  Hopefully ChatGPT will start offering this as the suggested answer.  It seems likely that many users will continue to be impacted by this meaningless error, DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError.

[berora56]

Salut a vous,
A date le probleme est persistent, de notre coté on a ajusté ceci:

1. https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-performance#optimize-perf... 
2. Revalidé les time out (MashupDSRTestConnectionTimeout) pour les passer de <value>00 :00:50</value> vers <value>00:05:00</value>

Mais , on continue a avoir le meme erreur:

• DM_GWPipeline_Gateway_AdoNetProviderOpenConnectionTimeoutError

Merci de partager vos essais car a date semble un erreur interne du service.

[johnh35]

We ended up getting these errors yesterday for all of our reports as well. What did you end up doing to resolve the issue?

[dbeavon3]

This product is built in a way that assumes you will open cases with Mindtree ("professional" support) whenever you have questions.   Be prepared to spend a couple hours gathering fiddler traces.

If you want to avoid that, you can restart your gateways, as a hail mary.  Then turn on enhanced logging and see if anything appears in the mashup logs.

The design of the product assumes that most users are non-technical and are able to waste a day or two with tech support.  Else they would give far better transparency into what is going wrong.  The error descriptions in the Power BI portal are so terrible it is almost comical. The information is rarely enough to tell if the problem is your bug or Microsoft's.  In my experience about 90% of these are Microsoft bugs so don't feel bad about opening a ticket.

[johnh35]

Thank you for the response. Did you end up solving the issue that you were having? If so, could you please share what was done to solve the issue?

[dbeavon3]

Hi @johnh35 ,

As I recall, the problem was on Microsoft's side. I recommend opening a case and asking for an RCA, especially if the problem lasts an extended period of time.

Microsoft is not very transparent about the connectivity bugs on their side, but hopefully they will share an increasing amount of information, as more customers are impacted by these same problems! 

FYI, There is a really buggy technology in Microsoft's networking stack called "private endpoints", and these infrastructure elements are often the cause of any mysterious connectivity issues (even within Microsoft's own software dependencies).  The worst part is that they are tremendously embarrassed by their private endpoint bugs and refuse to discuss them openly with their customers.  It makes for a lot of frustrating support cases.  Even if you upgrade to "unified" support, you will get very little transparency about the bugs in their network.  Good luck!

[lbendlin]

The error message says that the gateway was unable to reach the ADO data source (likely SQL Server) within the allotted connection period (likely 10 seconds).

Agree on the "make it human readable"  comment.

[dbeavon3]

Thanks @lbendlin 

I have never seen an error message about an unavailable resource which doesn't at least identify the name of the resource that is unavailable.  (Why does PBI always have these basic usability problems?  It often seems like the software is being designed by college interns or something like that. )

FYI, there is no customer SQL Server that is common to all of these datasets.  Is it possible Microsoft reaching out to its own SQL Server and failing? (That might explain why they don't want to tell the users the name of the Microsoft SQL resource that has fallen over and died.  They would rather we spend a three weeks with CSS support, or just wait a few days for the errors to go away on their own.)