Forum Discussion

DKHUghes55's avatar
DKHUghes55
Resolver I
8 months ago
Solved

On-Prem data gateway Timeout / Cancel errors on model processing

Hello Community, I am seeing error messages in the On-Prem Data gateway diagnostics.  They indicate the gateway cancelled the operation due to a timeout on a connection. Below is a snipit of the er...
Need Help
  • Zanqueta's avatar
    Zanqueta
    8 months ago

    Hi DKHUghes55,

     

    Is not a depper analysis but, looking at your message the error you are encountering in your On-Premises Data Gateway indicates that the operation was cancelled due to a timeout, specifically an AsyncOperationStreamingCancelledException.

     

    This typically occurs when the gateway is unable to maintain a connection to the data source or when the server hosting the gateway is under resource pressure.

     

    • Observation: The logs indicate a failure to query the ADServer (Query result is null on ADServer GC://hou99dcgcpk0001...).
    • You are using the June 2025 version of the gateway.
    • Recommendation:
      • Verify whether a newer version of the gateway is available and apply updates if so.
      • Microsoft frequently addresses bugs and improves stability in newer releases.

     

    If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

    Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

Anonymous's avatar
Anonymous
Not applicable
8 months ago

Hi DKHUghes55 ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

 

The error AsyncOperationStreamingCancelledException shows that the gateway is cancelling refresh because the AD lookup is timing out. Since your gateway is reaching high load (CPU ~95%, Memory ~85%), these directory queries are more likely to fail during processing.

Appreciate the points from Zanqueta  on updating the gateway version this is recommended, as newer builds include fixes for AD lookup stability. Also agree with lbendlin 2 regarding not exposing internal AD details.

Please do the following step helps you resolving your issue:

  • Update to the latest On-Premises Data Gateway.

  • Reduce heavy or concurrent refresh loads on the gateway.

  • Check AD connectivity (network/permissions) and avoid AD lookups during refresh if possible.

If the issue continues after these steps,please can review performance logs further.

Hope this helps. Please reach out for further assistance.

 

Thank you.