Forum Discussion
ServerError_DM_GWPipeline_Gateway_MonitoredDbConnectionError
- Anonymous1 year ago
Hi Anonymous ,
Sorry for late reply.This issue has been resolved, please upgrade the gateway to the October release (3000.242.5).
Best regards,
Community Support Team_ Scott Chang
I was able to captured some specific instances of the error, and identified that the issue is happening across all DirectQuery connections (8 Oracle DB connections, and Snowflake). I cannot find any common element between them. Since it's also happening with Snowflake, that rules out the possibility of it being an issue with the in-house DBs.
QueryExecutionReport reports "QueryExecution failed with error: Failed to retrieve connection: no connection with ID exists."
I did also find this "Object reference" error in GatewayError.log which matches up with the errors in GatewayInfo.log:
[DM.GatewayCore] Error while updating connection status. ConnectionId: c5480ca0-0add-414f-a2e6-cf54f47c9864 - System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Data.Mashup.MashupConnection.UpdateProgress(IEnumerable`1 progresses)
at Microsoft.Data.Mashup.MashupConnection.get_Progress()
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetStatusUtils.GetCurrentStatusFromMashupConnection(MashupConnection connection)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetMonitoredDbConnectionPool.GetAndProcessStatus(Guid connectionId, IAdoMonitoredConnection connectionWithStatus, Nullable`1 activeQueryIdToRemove)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetMonitoredDbConnectionPool.UpdateConnectionStatus(Guid connectionId)
Since 10-08-2024 we have exactly the same problem with direct query connections.
We get the 'ServerError_DM_GWPipeline_Gateway_MonitoredDbConnectionError'
with Gateway version: 3000.238.11
Where you able to identify the reason for this error?
- Anonymous1 year agoNot applicable
No, I haven't been ble to find anything. It's still happening consistently. I've been otherwise tied up and haven't had a chance to investigate further.
Thanks for commenting, and confirming that we're not the only one experiencing this issue since updating to 3000.238.11.
- Anonymous1 year agoNot applicable
Per lbendlin 's suggestion above, I have posted this in the Issues subforum https://community.fabric.microsoft.com/t5/Issues/Direct-Query-refresh-failures-after-upgrading-Gateway-3000-238/idi-p/4235334#M109713