Forum Discussion
On-premises gateway issue
- 1 year ago
Good morning,
the Microsoft support team suggested us to downgrade the gateway to an older version (October 2024).
With that version, we didn't faced the 9518 error anymore.
Hi DiegoPLAB ,
We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance. Once the issue is resolved please share the solution here to help others in the community.
Thank you
Good morning,
the Microsoft support team suggested us to downgrade the gateway to an older version (October 2024).
With that version, we didn't faced the 9518 error anymore.
- v-menakakota1 year agoCommunity Support
Hi DiegoPLAB ,
We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance.
If this is the solution that has worked for you please accept your reply as solution so as to help other community members who may face similar issue in the future.
Best Regards,
Menaka.
Community Support Team - Sephir10 months agoFrequent Visitor
I'm experiencing the same issue. Are there any other solutions besides downgrading? I can't determine why this is happening. Microsoft Support suggested increasing the server capacity, but the server appears to be performing well and is responsive (just had some spikes of 100% CPU for shor period of time).
- v-menakakota10 months agoCommunity Support
Hi Sephir ,
Thanks for sharing your case. From what we’ve seen in this thread, there seem to be two main directions:
- In one case, downgrading the gateway to the October 2024 version stopped the 9518 errors. It may be worth trying that if you haven’t already.
- Even if your SQL Server looks fine, short spikes in CPU or network can still cause this runtime busy error. Sometimes splitting the copy into smaller activities or running the pipeline when the server is less busy can help.
Since Microsoft Support is already involved, I’d suggest letting them know your exact gateway version and server load patterns. That will help confirm if this is a known gateway issue or something resource-related.
Best Regards,
Community Support Team