Forum Discussion
NuwanAthukorala
Advocate II
2 months agoData 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...
- 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. 😊😊😘😘
NuwanAthukorala
Advocate II
2 months agoHi,
Thank you for your response.
Please find the details below:
Source Type: Yes, the source system is on-premises.
Gateway Configuration: We are using a single-node On-Premises Data Gateway.
Scope of the Issue: The issue is not limited to a specific pipeline. We created a new simple Copy Data Activity for testing purposes, and it also failed with the same error (9518).
Capacity Metrics: We did not observe any significant workloads or long-running activities at the time of failure.
Workspace/Capacity Testing: Yes, we tested in other projects/workspaces, and the same error occurs consistently.
Impact: Currently, all Fabric Data Factory pipelines that use Copy Data Activities are affected and failing with the same runtime8 busy error.
Recent Changes: There have been no credential changes, capacity changes, or source system changes. The On-Premises Data Gateway is up to date and operating normally.
Additional Observations:
The same source connection works successfully in Dataflow Gen2.
Test Connection within Copy Data Activity also fails with the same error.
Since Dataflow Gen2 can access the source without issues, the source connectivity, credentials, and gateway configuration appear to be functioning correctly.
The issue seems to be isolated to the Data Factory Runtime used by Pipeline Copy Data Activities.
Could this be related to a backend Fabric Data Factory Runtime issue or a service-side limitation affecting Copy Data Activities?
Any guidance would be greatly appreciated.
Thank you.