Forum Discussion
Faulting application FabricPipelineWorker.exe
Hello,
we installed an On-premise data gateway version 3000.330.1 (August 2026) on a Windows Server 2025.
Every time we connect to SAP over SAP Table Application Server to our SAP System on SAP Cloud, we get the following error:
Application: FabricPipelineWorker.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MultiplexingMessenger.OnMessageToOtherChannel(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, MessageToOtherChannel)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.MessageHandlerSet.Dispatch(Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessageChannel, Microsoft.DataTransfer.Common.ProcessManagement.Communication.Message)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.Common.ProcessManagement.Communication.IMessengerExtensions+<WaitForAsync>d__1`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.Common.ProcessManagement.RemoteService.RemoteServiceEnvironment+<DisposeServiceStubsAsync>d__4.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.WorkerContainer+<StartAsync>d__11.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program+<Main>d__1.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.DataTransfer.DataMovementGateway.WorkerProcess.Program.<Main>(System.String[])
AND:
Faulting application name: FabricPipelineWorker.exe, version: 5.68.9706.2, time stamp: 0x900a871d
Faulting module name: KERNELBASE.dll, version: 10.0.26100.33158, time stamp: 0x4332201f
Exception code: 0xe0434352
Fault offset: 0x00000000000c75fa
Faulting process id: 0x2234
Faulting application start time: 0x1DD3B1901C52B57
Faulting application path: C:\Program Files\On-premises data gateway\FabricIntegrationRuntime\5.0\Shared\FabricPipelineWorker.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: a3bc643f-227b-4f9e-b7b7-45ff005eb05f
Faulting package full name:
Faulting package-relative application ID:
Has anyone an idea?
BR Thomas
We are on newest Gateway version, 3000.338.2 (October 2026) and Windows Server 2025.
At the moment the Power BI team don't reports errors.
10 Replies
dprenc_elixirrAdvocate IV
I can confirm that in our case, newest version (3000.338.2.) also seems to be working fine
Shubham_rai955Super User
A few things I would check:
- Gateway version: Update to the latest available on-premises data gateway version and check if the issue persists.
- SAP connector dependencies: Verify that the required SAP .NET Connector (NCo) components are installed and compatible with the gateway environment.
- Isolation test: Try connecting to the same SAP system using the SAP connector outside Fabric, if possible. This can help isolate whether the issue is with SAP connectivity or the gateway worker.
- Logs: Check the gateway logs around the failure timestamp. The System.InvalidOperationException alone does not reveal the underlying cause.
One thing worth investigating is whether this happens only with the SAP Table Application Server connector or with other SAP connections as well.
If it consistently crashes with this connector, I would recommend raising a Microsoft support ticket with the gateway logs and crash dump. This may require investigation by the Fabric Data Factory team.
We are on newest Gateway version, 3000.338.2 (October 2026) and Windows Server 2025.
At the moment the Power BI team don't reports errors.
- dprenc_elixirr
Is there any update on this issue?
We have updated both the On-premises Data Gateway and the SAP .NET Connector to the latest versions available to us, but we are still experiencing crashes. We have also disabled load balancing, but this has not resolved the issue.
Interestingly, we do not see any errors in Microsoft Fabric itself. Based on our investigation, it appears that FabricPipelineWorker.exe crashes after all operations have completed successfully, potentially when attempting to close existing SAP connections.
In the On-premises Data Gateway logs, we can see that the Copy activities return Status: Succeeded, which suggests that the data transfer itself completes successfully - that is the reason why in Fabric everything looks okay.
However, these crashes are generating a very large number of error logs on the SAP side. That is very frustrating and it is triggering a lot of unnecessary alerts.
Our current environment:
- On-premises Data Gateway: 3000.334.4
- Microsoft C++ Runtime 14.x: 14.50.35719.0
- SAP .NET Connector: 3.1.8.0
Has anyone experienced similar behavior or received any updates from Microsoft regarding this issue?
v-saisrao-msftCommunity Support
Hi ThomasPluemper,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
- v-saisrao-msft
HI ThomasPluemper,
Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.
Thank you.
- v-saisrao-msft
Hi ThomasPluemper,
First, verify that the gateway server has the required SAP NCo 3.1 (64-bit) and Microsoft C++ Runtime 14.x prerequisites. Also verify the SAP Application Server connection details, including the server, client, and system number. Then enable the documented SAP/gateway diagnostic logging and reproduce the issue so that we can capture more details about the SAP connection failure. Since the error shows FabricPipelineWorker.exe terminating unexpectedly, the additional logs should help determine whether the issue is related to the SAP prerequisites/connectivity or to the Fabric gateway runtime itself.
SAP ERP - Connectors | Microsoft Learn
SAP Table Application Server connector overview - Microsoft Fabric | Microsoft Learn
Troubleshoot the on-premises data gateway | Microsoft Learn
Thank you.Hello,
On-premise data gateway: 3000.330.1
Microsoft C++ Runtime 14.x: 14.50.35719
SAP NCo 3.1 (64-bit) : 3.1.7.0I have the same event on different servers with On-oremise data gateway.
Where to look in the log files?BR Thomas
- v-saisrao-msft
Hi ThomasPluemper,
You can check the gateway logs on the gateway server under %LOCALAPPDATA%\Microsoft\On-premises data gateway\ when using the age-based log retention configuration. The relevant log files are GatewayInfo*.log, GatewayError*.log, and GatewayNetwork*.log, and the timestamps are in UTC. You can also open the On-premises data gateway app → Diagnostics → Gateway logs to export the gateway logs as a ZIP.
Use the on-premises data gateway app | Microsoft Learn
Configure log files for the on-premises data gateway | Microsoft Learn
Troubleshoot the on-premises data gateway | Microsoft LearnThank you.
- dprenc_elixirr
Following, we are experiencing exact same error