Forum Discussion
PowerBI report refresh gateway error
Hi hcirak,
Thank you for the update. Since the issue persists after verifying the gateway configuration and connectivity and the error message is too generic to identify the root cause, please provide below details to investigate further.
- What type of data source are you connecting to?
- Does the issue affect all datasets using this gateway or only this specific dataset?
- Did the issue start immediately after upgrading to the June gateway version, or did it begin later?
- Check if there are any additional error messages in the On-premises data gateway logs around the time of the failed refresh
Also, if you are still running the june gateway version, update the gateway to the latest on-premises data gateway version, restart the service and check if the issue persists.
Thanks and regards,
Anjan Kumar Chippa
Hello,
- What type of data source are you connecting to? --SQL Server and Oracle
- Does the issue affect all datasets using this gateway or only this specific dataset? --Spesific semantic models were affected
- Did the issue start immediately after upgrading to the June gateway version, or did it begin later? --Actually we were having this problem sometimes and solving by upgrading gateway. But after the latest upgrade, this problem has arised again.
- Check if there are any additional error messages in the On-premises data gateway logs around the time of the failed refresh -- I am sharing some error messages we got below.
DM.EnterpriseGateway Error: 0 : 2026-07-20T17:53:35.8634982Z DM.EnterpriseGateway ef696dae-a770-4fe0-9d8e-0570df15dc05 86716627-2f07-409e-abfd-05544be394cb MGAP 11c8d1d3-db61-4711-a460-07d71b759413 7ab698bd-5293-48e4-ab7b-188a5a87772a f8231f74-05bb-4e3a-ae78-2efe26d93f03 8B21C03B [DM.Pipeline.Diagnostics] Exception object created [IsBenign=True]: Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.UnknownSpooledOperationIdException: The spooled operation id f9b526a2-99ec-479e-9066-e86e3f3cb18e does not exist. Evict code: -1.; ErrorShortName: UnknownSpooledOperationIdException
DM.EnterpriseGateway Error: 0 : 2026-07-20T17:53:35.8645009Z DM.EnterpriseGateway ef696dae-a770-4fe0-9d8e-0570df15dc05 86716627-2f07-409e-abfd-05544be394cb MGAP 11c8d1d3-db61-4711-a460-07d71b759413 7ab698bd-5293-48e4-ab7b-188a5a87772a f8231f74-05bb-4e3a-ae78-2efe26d93f03 952FAEE2 [DM.Pipeline.Diagnostics] StackTrace: at Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.UnknownSpooledOperationIdException.TraceConstructor()
DM.EnterpriseGateway Error: 0 : 2026-07-20T17:53:35.8645009Z DM.EnterpriseGateway ef696dae-a770-4fe0-9d8e-0570df15dc05 86716627-2f07-409e-abfd-05544be394cb MGAP 11c8d1d3-db61-4711-a460-07d71b759413 7ab698bd-5293-48e4-ab7b-188a5a87772a f8231f74-05bb-4e3a-ae78-2efe26d93f03 590DBA9A [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=1, err=UnknownSpooledOperationIdException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2026-07-20T17:53:35.8654974Z DM.EnterpriseGateway 618788b8-dd75-4923-92c9-f3f565a19492 86716627-2f07-409e-abfd-05544be394cb MGPP 11c8d1d3-db61-4711-a460-07d71b759413 7ab698bd-5293-48e4-ab7b-188a5a87772a f8231f74-05bb-4e3a-ae78-2efe26d93f03 590DBA9A [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=1, err=UnknownSpooledOperationIdException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2026-07-20T17:53:35.8654974Z DM.EnterpriseGateway caaeaaa7-40d8-4049-b772-0cfd2a9b9ac6 86716627-2f07-409e-abfd-05544be394cb MDSR 11c8d1d3-db61-4711-a460-07d71b759413 7ab698bd-5293-48e4-ab7b-188a5a87772a f8231f74-05bb-4e3a-ae78-2efe26d93f03 4C1EF73E [DM.GatewayCore] Error processing request: [0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.UnknownSpooledOperationIdException: The spooled operation id f9b526a2-99ec-479e-9066-e86e3f3cb18e does not exist. Evict code: -1.
Hi hcirak,
Thank you for providing the additional details.
Since the issue affects only specific semantic models and updating the data source credentials also not worked and the error message is too generic to identify the root cause, this does not look like a standard gateway configuration issue.
- I recommend opening a Microsoft Support ticket and include the failed refresh error details, the gateway logs from the time of the failure, the affected semantic model names, the data source details (sql server and oracle) and the gateway version.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa