Scheduled refresh suddenly failed：DM_GWPipeline_Gateway_SpooledOperationMissing

[qqqhair]

Hello everyone!

The scheduled refresh suddenly failed, I suddenly encountered the following issue:

{"error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","pbi.error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","parameters":{},"details":[],"exceptionCulprit":1}}} Table: history query.

gateway Log：Received error payload from gateway service with ID 275727: The spooled operation id d5e23c85-bd20-444e-9d36-d3e11b665b20 does not exist. Evict code: -1..;The spooled operation id d5e23c85-bd20-444e-9d36-d3e11b665b20 does not exist. Evict code: -1.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: tainan_attractions.

I have tried the following:

• Restarted the on-premises data gateway service.
• Updated the Power BI gateway to the latest version.

Do you have any suggestions on how to resolve this issue?

Thank you in advance!

[Anonymous]

Hi @qqqhair , 

Have you solved your problem? If it is solved, please share your solution and accept it as solution or mark the helpful replies, it will be helpful for other members of the community who have similar problems as yours to solve it faster. Thank you very much for your kind cooperation!

Best Regards,
Zhu

[qqqhair · Accepted solution]

Thank you for your replies and assistance. Here’s an update on the process of resolving this issue. I attempted to configure the gateway’s disk space, but the problem persisted. Finally, after clearing the temporary files in Windows, scheduling was able to proceed smoothly.

[Anonymous]

Thanks for the reply from Idrissshatila.

Hi @qqqhair ,

By default, the limit for the number of queries that can run simultaneously on a gateway node is 40. Hitting this limit often will cause incoming queries to get queued pending to run for a long time, which will result in performance degradation and timeout type of errors. Please try to reduce the number of queries or use an incremental refresh strategy.

Here are some helpful documents for you:

Monitor and optimize on-premises data gateway performance | Microsoft Learn

Plan, scale, and maintain a business-critical gateway solution | Microsoft Learn

Best Regards,
Zhu
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.

[Idrissshatila]

@qqqhair ,

can you try to refresh it manually in service?

[IrisTseng]

@Idrissshatila 

Unfortunately, manual refresh in service failed.

[Idrissshatila]

Hello @qqqhair ,

test the following:

• Review the queries behind these tables (history query, tainan_attractions) to ensure there are no syntax errors or timeouts when accessing the data sources.
• Test the queries manually in Power BI Desktop to see if they work without the gateway.
  
  Also, Subscribe to my channel https://www.youtube.com/@PowerBISolution

[qqqhair]

Thank you for your reply. After checking the history query and tainan_attractions these table, there are no syntax errors or timeouts. The source can be refreshed and published without issues in Power BI Desktop, but the Scheduled Refresh fails.