FabricPipelineWorker.exe crash when using with SAP connection

FabricPipelineWorker.exe crashes after successful SAP Copy activity – On-premises Data Gateway

Hello Microsoft Fabric Community,

We are experiencing recurring crashes of FabricPipelineWorker.exe when using Microsoft Fabric Data pipelines to extract data from SAP through the SAP Table Application Server connector and an On-premises Data Gateway.

The issue appears to be similar to the one reported in this discussion:  Faulting application FabricPipelineWorker.exe

However, despite updating the relevant components and changing the gateway configuration, the issue persists.

Issue description

The interesting part is that Copy activities complete successfully in Microsoft Fabric, and we do not see any errors or failed pipeline executions in Fabric itself.

In the On-premises Data Gateway logs, the Copy activities also return:

Status: Succeeded

However, FabricPipelineWorker.exe appears to crash after the data transfer has completed, potentially during the cleanup phase when existing SAP connections are being closed or disposed of.

This is currently our assumption based on the observed behavior, rather than a confirmed root cause.

Although the operations complete successfully, these crashes generate a very large number of error logs on the SAP side, creating additional operational overhead and making monitoring more difficult.

Environment

• On-premises Data Gateway: 3000.334.4
• Microsoft C++ Runtime 14.x: 14.50.35719.0
• SAP .NET Connector (NCo): 3.1.8.0

Troubleshooting performed

We have already taken the following steps:

1. Updated the On-premises Data Gateway to version 3000.334.4.
2. Updated the SAP .NET Connector to version 3.1.8.0.
3. Verified the Microsoft C++ Runtime version.
4. Disabled gateway load balancing to rule out potential issues with connections being distributed across gateway nodes.
5. Reviewed the gateway logs and confirmed that Copy activities report successful completion.

Unfortunately, none of these changes has resolved the issue.

Since the data transfers themselves are successful, this appears to be more related to the gateway worker process lifecycle or SAP connection cleanup than to SAP connectivity or data extraction.

Any insights from the Microsoft Fabric engineering team or others experiencing similar behavior would be greatly appreciated.