Direct Query refresh failures after upgrading Gateway (3000.238.11) with MonitoredDbConnectionError

[aaronhaviland]

Following on from this Forum post https://community.fabric.microsoft.com/t5/Service/ServerError-DM-GWPipeline-Gateway-MonitoredDbConne... (Please see that post for relevant logfile snippets)

After upgrading the gateway to the latest version, roughly 1/3 of all Direct Query queries are reporting error ServerError_DM_GWPipeline_Gateway_MonitoredDbConnectionError in BI Service. From what I've been able to determine, it happens to all reports that use Direct Query, regardless of the direct query data source.

The only connection we can find is that all the errors are using Direct Query. Import Refreshes don't seem to experience this issue.

Additionally, this error message isn't documented anywhere that I've been able to find.

[BarSi1986]

same thing here, since last week there is exact the same problem with direct queries on pbi service, gateway v.  3000.238.11 (September 2024) 

also i have problems with import queries with adnotation that ODAC was not found on the system wchich is not true cause there is ODAC installed and till last week everything was fine

[malarkey99]

I deinstalled the gateway 3000.238.11

and reinstalled the older july version

with recovery key, now it's working again.

[ashleyodonnell]

We are seeing the same issue after upgrading our Gateway to 3000.238.11 version. 

[MaZoSR]

Microsoft has released a new version yesterday (3000.242.5), however we're still experiencing issues with Databricks connections failing due to a certificate exception (which started after we had upgraded to the September version).

[aaronhaviland]

It appears the 3000.242.5 version may have resolved this specific issue.

However, since the issue initially did not present itself until a few days after upgrading to 3000.238.11, and without any confirmation of the issue from MS, or any changelog documenting the fix, I'm hestitant to say this is resolved. I will monitor the gateway logs, and I will report back in a few days.

[Eric_Dommisse]

We work with version 3000.238.11 and also have the problem, so that is not the solution.

[JDN1986]

We had the same issue with version 3000.238.11 after updating to version 3000.242.5 our issue at his moment is resolved.

[Tomato0023]

Hello,
The first day with version 3000.242.5 went without any problems.
It seems that the problem is solved.
If anything changes I will let you know.
I am still testing

[Anonymous]

Hi all,

This issue has been fixed, please try it again.

Thanks for your patience！

Best regards.
Community Support Team_Caitlyn