DM_GWPipeline_Gateway_SpooledOperationMissing and DM_GWPipeline_Gateway_DataSourceAccessError error.

[juliobrito]

Hola y gracias de antemano.
Resulta que tengo un informe que estoy intentando actualizar.
A veces genera el código de error "DM_GWPipeline_Gateway_SpooledOperationMissing"
y otras veces el código de error "DM_GWPipeline_Gateway_DataSourceAccessError".
Les atreveré un poco de contexto. Les diré que este es un informe complejo.
Sospecho que los problemas comenzaron justo después de agregar una segunda puerta de enlace y formar un clúster.
Puede que esto no esté relacionado, pero lo menciono.
Lo cierto es que este informe en particular, y también otros, han comenzado a fallar gradualmente con estos dos códigos de error mencionados.
¿Tienes alguna información sobre un error similar?
Cualquier consejo sería muy útil.
¿Es un error?

[v-pagayam-msft]

Hi @juliobrito ,
I wanted to follow up on our previous suggestions regarding the error you are facing. We would like to hear back from you to ensure we can assist you further.
If our response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.

Thank you.

[v-pagayam-msft]

Hi @juliobrito ,

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

These errors are related Gateway connectivity issues, cluster misconfigurations, or authentication failures. Below steps might help to resolve the issue:

DM_GWPipeline_Gateway_SpooledOperationMissing:

• Go to Manage Gateways in Power BI Service and ensure all gateways in the cluster are online and healthy.
• If different gateway nodes in a cluster run different versions, queries may fail. Ensure all nodes are updated to the latest version.
  

DM_GWPipeline_Gateway_DataSourceAccessError:

• If credentials were changed or expired, the gateway may unable to authenticate. Update credentials in Manage Gateways.
• Ensure the account used for authentication has read permissions on the data source.
  

For further troubleshooting steps, please refer to the official Microsoft documentation

Let me know if you need additional assistance!

If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

[juliobrito]

Hello everyone.
Although the problem persists, its occurrence has decreased.
Reviewing logs, we've identified a possible cause of insufficient RAM.
Although we've upgraded our resources at certain times, we're still receiving these errors.
Best regards.

[v-pagayam-msft · Accepted solution]

Hi @juliobrito ,
Great to hear the issue has reduced!
Low RAM can still cause errors, so monitoring CPU and memory usage during refreshes is key. If usage spikes, consider increasing RAM or virtual memory. Optimizing queries, reducing refresh frequency, and avoiding heavy background processes can also help.

Hope this helps.If so, please Accept the answer so that it will be helpful to others to find it quickly.