Error during pipeline creation to read from a SQL Server: The Data Factory runtime is busy now

[pmscorca]

Hi,

I need to import data from a SQL Server on-premise source.

So, I've

• installed the OPDG in a local machine using a local user account with the necessary administrator privileges;
• registered the installed OPDG using a Microsoft Entra ID service account;
• tested the installed and registered OPDG;
• shared with my Microsoft Entra ID account the data gateway in Fabric;
• created the on-premise connection using my Microsoft Entra ID account in Fabric.

I'm working in a new Fabric environment (F8 capacity), inside a new and unique workspace. My Microsoft Entra ID account has the admin role for this workspace.

In Fabric, I've checked the status of the data gateway and the related connection: they are on-line.

I'm trying to create the first pipeline with a copy activity: I've specified the connection, the connection type (SQL Server) and then I've run the test connection obtaining this error (error code = 9518):

In the Fabric environment there aren't any other pipelines or dataflow gen2s.

Well, any helps to me in order to solve a such strange issue, please?

Many thanks

Update this post: I've tried with both November 2025 and October 2025 OPDG, but the issue remains. Thanks

[spaceman127 · Accepted solution]

Hi @pmscorca ,

That is a crucial clue.

According to the installation file for the November update, official support is only provided up to Windows Server 2022.

I think this is where the problem lies. Even if you were able to install it, that doesn't mean it will work again.
Officially, 2025 is not yet supported.
Of course, there is no mention of this in the documentary.

See screenshot.

 

Here the documentation again.

https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install#requirements

Please install the On Premise Data Gateway on Server 2019 or Server 2022. If that doesn't work, you could contact support. 

If it works, then we can help you with your other problem, if it has already been solved with this.

Best regards 

[v-nmadadi-msft]

Hi @pmscorca 

May I check if this issue has been resolved by points provided by @spaceman127 ? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @pmscorca 

I wanted to check if you had the opportunity to review the valuable information provided by @spaceman127 . Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft]

Hi @pmscorca ,
Thanks for reaching out to the Microsoft fabric community forum.

In addition to the valuable point mentioned by @pmscorca , Please check out this point which test if the issues lies with lack of access to ports.

To test if the gateway has access to all the required ports, run the network ports test. The results of the test are either Completed (Succeeded) or Completed (Failed, see last test results). If the test succeeded, your gateway successfully connected to all the required ports. If the test failed, your network environment might be blocking these required ports and servers.

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

[spaceman127]

Hi @pmscorca,

I suspect it's an authorization issue.

From what I gather from your description, the gateway connection is working and you have access.

But what interests me now is, what credentials are you using to establish the connection?
I suspect that's where the problem lies.

When establishing the connection, could you switch to Basic for a moment and use SQL Server authentication, then test it?

I assume you've already worked through the Microsoft articles on this topic.

Best regards

[pmscorca]

Hi, thanks for your replies.

Inside Fabric, I need to use connection with basic authentication (SQL Server authentication): it is the unique authentication mode that I can use.

After I've uninstalled the November 2025 OPDG and I've installed the October 2025 one I've noticed that the network ports test fail; so I've uninstalled and reinstalled the October 2025 OPDG but the setup fails with this error (code = 1601):

It's very hard to understands the logs.

I need to solve the setup issue as the first thing.

Thanks

[spaceman127]

Hi @pmscorca ,

The error is definitely a Windows installation error.

Have you checked the system requirements?

https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install#requirements

I've had this error before, and here's what I did.

1. Uninstall
2. Restart the system
3. Install

That worked by me.

If that doesn't help, you'll need to check whether there are any old directories or remnants on your system that are preventing a new installation.

Best regards

[pmscorca]

Hi, thanks for your reply.

I'm trying to reinstall after the uninstallation and the restarting of the machine but unsuccessfully.

Which could be the remnants to eliminate? Thanks
It's very hard to understands the logs.

[spaceman127]

Hi @pmscorca ,

first.

Can you Share your Logs?

And here you find an other article to clean the installation.

That would be my first step.

https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Can-t-uninstall-on-premise-gateway/m...

Best regards 

[pmscorca]

Hi,

I've tried to delete register keys related to the OPDG and the remnants folders, but unsuccessfully.

I've tried to reinstall the November 2025 version, but unsuccessfully.

I've checked the .NET Framework: is the 4.8 one.

The operating system is Windows Server 2025 Datacenter.

I remember that I've installed the November 2025 version successfully, I've uninstalled it successfully to install the October 2025 version successfully and then I uninstalled it successfully.

I think that an important software like OPDG should have a separate or integrated certified tool that allows you to check the prerequisites and clean up in case of uninstallation; by this software it is possible to connect to on-premise data sources!
It doesn't seem a more stable software: some users have solved in a manner, other users in another manner, and so on.

[spaceman127 · Accepted solution]

Hi @pmscorca ,

That is a crucial clue.

According to the installation file for the November update, official support is only provided up to Windows Server 2022.

I think this is where the problem lies. Even if you were able to install it, that doesn't mean it will work again.
Officially, 2025 is not yet supported.
Of course, there is no mention of this in the documentary.

See screenshot.

 

Here the documentation again.

https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install#requirements

Please install the On Premise Data Gateway on Server 2019 or Server 2022. If that doesn't work, you could contact support. 

If it works, then we can help you with your other problem, if it has already been solved with this.

Best regards 

[pmscorca]

Ok, but it is strange that I've installed the gateway with success the first time.

However, the software doesn't seem more stable and it could have a certified tool to check the hw-sw requirements and clean the machine after an uninstallation, without reading hard logs to understand.

[spaceman127 · Accepted solution]

Hi @pmscorca ,

of course, that cannot be explained.

Please let us know if you have installed it on a different server operating system.
If your original problem still persists, we can then continue to investigate.

Feel free to leave kudos or accept it as a solution. This will also help other community members.

Best regards