Power BI Error: DM_GWPipeline_Gateway_SpooledOperationMissing – Gateway Data Operation Issue

Hi lariane ,

Welcome to the Power BI Community.

This is a somewhat rare but specific error. The DM_GWPipeline_Gateway_SpooledOperationMissing error essentially means that the Power BI Service tried to retrieve a result set that the Gateway had supposedly prepared (spooled), but the Gateway could not find it.

This usually happens for one of three reasons:

1. The Gateway Service Restarted: If the On-Premises Data Gateway service crashed or restarted during the query execution, the temporary "spool" files are lost.

2. Disk Space Issue: The Gateway machine ran out of disk space while trying to buffer (spool) a large dataset.

3. Aggressive Cleanup: An antivirus or system process deleted the temporary files in the Gateway's spool directory.

Here are the troubleshooting steps to resolve this:

1. Restart the Gateway Service This is the most effective immediate fix.

• Log in to the machine running the Gateway.

• Open the On-premises data gateway app.

• Go to Service Settings and click Restart now.

• Alternatively: Open Windows Services (services.msc), find "On-premises data gateway service," and restart it.

2. Check Disk Space If you are pulling a large amount of data, the Gateway needs significant space to "spool" that data before sending it to the cloud.

• Check the drive where the Gateway is installed (usually C:\).

• Ensure there is ample free space (at least 2-3 times the size of the dataset you are refreshing).

3. Update the Gateway Since today is December 29, 2025, ensure you are running the latest version (likely the December 2025 or November 2025 release). Older versions may have memory management bugs that cause the service to crash and lose the spooled operation.

4. Check for "Double Hop" or Network Latency If this error persists, it might be due to a network timeout between the Gateway and the Data Source, causing the spooling session to expire.

• Try reducing the amount of data (filter by date) to see if a smaller dataset succeeds.

Start with a simple service restart; that solves this issue 90% of the time.

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.

During refresh, the gateway temporarily stores (“spools”) data on the gateway machine. If that spooled data can’t be found (because the gateway restarted/crashed, disk/temp was cleaned, AV deleted it, or the gateway install is unstable), the Service throws DM_GWPipeline_Gateway_SpooledOperationMissing.

1. Update the on-premises data gateway to the latest version
   This error has been associated with specific gateway builds and fixes in later releases. 

2. Restart the gateway service (On-premises data gateway service)
   If it’s intermittent, this often clears it.

3. Check disk space + temp cleanup on the gateway server

   • Ensure the gateway machine has free disk space

   • Make sure no scheduled cleanup/AV is deleting gateway temp/spool files mid-refresh

4. Check for duplicated/cloned gateway machines
   If the gateway host VM was cloned and both instances run with the “same” identity/config, the service can get confused and throw spooling errors; uninstall/disable the duplicate gateway.

5. If it only happens for one dataset
   The gateway error can sometimes mask the real underlying query/data issue (e.g., refresh cancellation due to a data problem). Try refreshing smaller subsets / check gateway logs for the real root error.