topic Re: Copy activity error when Destination is on prem SQL Server in Pipelines

Copy activity error when Destination is on prem SQL Server

schneiw — Wed, 17 Dec 2025 16:20:35 GMT

I am trying to copy data from a lakehouse table to an on prem SQL Server table (using insert). I thought I had tested it successfully a month or so ago, but I cannot get it to work now. The message mentions "Invalid type 'LakehouseSql" and "linkedServices" but in my FABRIC interface there is no such mention of anything like that....

ErrorCode=UserErrorInvalidPluginType,'Type=Microsoft.DataTransfer.Common.Shared.PluginNotRegisteredException,Message=Invalid type 'LakehouseSql' is provided in 'linkedServices'. Please correct the type in payload and retry.,Source=Microsoft.DataTransfer.ClientLibrary,'

Re: Copy activity error when Destination is on prem SQL Server

mabdollahi — Thu, 18 Dec 2025 08:24:58 GMT

Hi schneiw

This usually happens when the pipeline is still using an old connection type.

LakehouseSql was used earlier for the Lakehouse SQL endpoint, but Fabric doesn’t support that linked service type anymore. So when the pipeline runs, Fabric can’t recognize it and throws that error.

What to do:

Remove the existing Lakehouse connection in your Copy activity
Create a new source connection and choose Lakehouse (not LakehouseSql)
Leave SQL Server as the destination (using the gateway if it’s on-prem)

Your data and SQL are fine — it’s just an outdated connection definition.

Regards,
Mehrdad Abdollahi

Re: Copy activity error when Destination is on prem SQL Server

schneiw — Thu, 18 Dec 2025 12:21:19 GMT

Thaks for that. However, the Connection is already a "Lakehouse":

Re: Copy activity error when Destination is on prem SQL Server

apturlov — Thu, 18 Dec 2025 22:29:32 GMT

Hi schneiw, as mabdollahi mentioned, the connection for Lakehouse in Fabric had multiple changes over the last few months. If your implementation was working a few months ago it could be outdated now. Rather then use a previously created connection, you need to reconfigure your Source in the Copy activity. In the new style you actually don't need to create a connection to the Lakehouse for the copy activity data source if you have access to the Lakehouse. You can just select a Lakehouse directly from the list of data sources in Fabric without having an connection object. First click Browse All

and then View More

On the next screen you'll the list of all your available data sources that you can just select as a data source in the Copy activity.
Keep in mind, with this configuration the data pipeline will try to use your connection to the Lakehouse when executing. It amy not work in all scenarios. If you are building an automated pipeline then you do need to create a Lakehouse connection and use that instead preferrably using a different organizational account.

If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.

Re: Copy activity error when Destination is on prem SQL Server

mabdollahi — Fri, 19 Dec 2025 07:15:56 GMT

I see. and I do have the same connection that works for me as I created it few min ago.
Have you tried creating a new connection? Sometimes, the recreation works due to some unseen issues behind the scene.