Forum Discussion

NuwanAthukorala's avatar
NuwanAthukorala
Advocate II
2 months ago
Solved

Data Factory Runtime Busy Error (9518) in Copy Data Activity, but Same Connection Works in Dataflow

Hi Team, We are experiencing an issue in Microsoft Fabric Data Factory.   Error Message:     Issue Details: The error occurs when executing a Pipeline Copy Data Activity. The source and...
data engineering
data pipeline
  • NuwanAthukorala's avatar
    NuwanAthukorala
    2 months ago

    Hi Team,

    Thank you for your guidance.

     

    We reviewed the Integration Runtime logs and found repeated errors:

     

    "Not enough resources to start a new worker. Current workers count: 0."

     

    After investigating the gateway server, we found that several applications were running and consuming server resources. We stopped the unnecessary applications and retried the connection test.

     

    After freeing up server resources, the Copy Data Activity and connection test started working successfully.

     

    This confirms that the issue was related to insufficient resources on the server hosting the On-Premises Data Gateway / Integration Runtime, preventing worker processes from being created.

     

    Thank you for helping us identify the root cause. 😊😊😘😘

v-shchada-msft's avatar
v-shchada-msft
Community Support
2 months ago

Hi NuwanAthukorala,
Thank you for reaching out to the Microsoft Fabric Community Forum.

Thank you for the additional details. Since Dataflow Gen2 continues to work while Pipeline Copy Activities consistently return Error 9518, the issue appears more likely related to the Integration Runtime (IR) or pipeline execution path rather than source connectivity itself. According to Microsoft documentation, the Integration Runtime is the compute infrastructure used by Data Factory pipelines, which suggests the issue may be occurring within the runtime path used by Pipeline activities (Integration runtime - Azure Data Factory & Azure Synapse | Microsoft Learn).

I would recommend reviewing the health of the On-premises Data Gateway, restarting the gateway service, and checking the gateway logs for any runtime or communication-related errors. It would also be worth verifying whether there are any service health issues in your region and testing with an alternative source connection.

If the issue persists, consider raising a Microsoft Support ticket. Be sure to include the troubleshooting steps already performed, as this will help speed up the investigation.

Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

I hope this information helps. Please do let us know if you have any further queries.

Regards.