On-premises gateway issue

[DiegoPLAB]

Good morning,

in our trial subscription we face an issue using on-prem gateway to ingest data from a local SQL Server instance.

We built a pipeline with a Copy Data activity, that connects to our on-premise SQL Server and copies data from several tables. The pipeline has other activities (notebooks, data flows...) and they all run successfully. But when we execute again the pipeline, we face a connectivity error on Copy Data activity (error code 9518), related to the source database.
The gateway is still active and its status results online on Fabric connections page.
To get it work again, we have to wait for several days. However, after a pipeline run, the problem get back.

Someone else faced this issue, but no clear solution was given:
https://community.fabric.microsoft.com/t5/Data-Pipeline/The-Data-Factory-runtime-is-busy-now-Please-...

https://community.fabric.microsoft.com/t5/Data-Engineering/Error-Code-9518/m-p/4661228

https://community.fabric.microsoft.com/t5/Data-Engineering/connector-to-on-prem-gateway-error-The-Da...

Our trial subscription is in West Europe area.

[v-menakakota]

Hi @DiegoPLAB  , 

Thanks for reaching out to the Microsoft fabric community forum. 

After a failure, try restarting the "On-premises data gateway" service  this often restores connectivity.
Please go through the below documents which may help you in resolving the issue:
On-premises data gateway in-depth - Power BI | Microsoft Learn
Troubleshoot the on-premises data gateway | Microsoft Learn

Have you tried to unintall and re-install the latest version of the enterprise gateway?

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Menaka.
Community Support Team  

[DiegoPLAB]

Hi @v-menakakota,

unfortunately me and my colleagues aren't admin of the gateway, since it was installed by the owner of the SQL Server local machine. So, we aren't able to restart on reinstall the gateway by ourserlves.
We asked him to restart the gateway some days ago, but this not solved the problem.
We are going to check the documents you shared and try other solutions.
Thanks.

[v-menakakota]

Hi @DiegoPLAB ,

We really appreciate your efforts and for letting us know the update on the issue.
Make sure the linked service for the SQL Server source is using the correct self-hosted integration runtime (matching the gateway you have installed).
If you're copying multiple tables in a single activity or pipeline, consider breaking it down into smaller parts to reduce resource demand.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka.
Community Support Team  

[DiegoPLAB]

Hi @v-menakakota,

we don't think it's a resource consumption problem in our capacity, as you can see above in the reply to Srisakthi.

In that reply, you can see the exact error message. Everithing appears to be correctly configured and active/online (both gateway and connection) in the Fabric connections page. But when we test the connection inside an activity, the test fails with error 9518.

[v-menakakota]

Hi @DiegoPLAB ,
Thanks for the update and the details you’ve shared.

Since the gateway is online, the configuration looks correct, and you’re still seeing Error 9518 during the activity, this may be an issue with the backend Data Factory runtime, especially in a trial environment.

If you are still unable to solve the issue you can reach out to Microsoft Support by raising a ticket with Microsoft Support. 

Please refer below link on how to raise a contact support or support ticket. 
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn 


If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka.
Community Support Team  

[v-menakakota]

Hi @DiegoPLAB ,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[DiegoPLAB]

Hello @v-menakakota ,

we raised a support ticket on friday. For now, the problem has not been solved yet.

[v-menakakota]

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

[DiegoPLAB · Accepted solution]

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-menakakota]

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 

[Srisakthi]

Hi @DiegoPLAB ,

As your using trial account, can you check the capacity metrics app. Failure can happen on many cases like capacity units are insufficient, or your local server unavailable. Could you please share the screenshot of error?

Regards,

Srisakthi

[DiegoPLAB]

Hi @Srisakthi,
we don't think that the issue is related to insufficient CU, as you can see from the screenshot below.

This is the screenshot of the error: