Error when using Copy data assistant with SQL Server connection

[amaaiia]

Hi,

I've been using a SQL Server connection to ingest data with COPY activity in a Data Pipeline for months, and I still can do it: 

Now, I've tried to use Copy data asisstant but I get an error with the same connection:

Any ideas about why is this happening only with Copy data assistant?

[v-cboorla-msft]

Hi @amaaiia 

Thanks for using Microsoft Fabric Community.

Aplogies for the inconvenience.

In my attempt to reproduce the "TypeError: cannot read properties of undefined (reading 'type')" error you described, I successfully established a connection to SQL Server using the Copy Data Assistant. Please find the screenshots for reference.

Copy activity using "Add to canvas"

Copy activity using "Use copy assistant"

There might be a chance of an intermittent issue could you please follow the below steps that might help you.

Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.

Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.

Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).

If the issue still persists, please do let us know. Glad to help.

I hope this information helps.

Thank you.

[NassBhorr]

Hi,

Thanks for the suggestion, but facing the same error and none of this works. It's weird because older pipelines withs same connection work no problem, and new dataflows with same connection also work. Is just the copy activity in a pipeline that is showing the error. SQL Server connection through local gateway. Always getting this:

 Any advice will be appreciated, been stuck in this for a couple days now.

Thanks,

[amaaiia · Accepted solution]

Hi @NassBhorr ,

I've been talking to support team:

1. The error message had been fixed and will apply to all regions by the end of week.

2. As a workarround, when Copy data assistant is used you can select the connection from OneLake data hub instead of from Home>SQL Server database and it works. However, they are still investigating on this.

[NassBhorr]

Yeah! That worked, accesing the connection hrough "Onelake data hub".

Thanks! 

[v-cboorla-msft]

Hi @amaaiia 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thank you.

[v-cboorla-msft]

Hi @amaaiia 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. If you have any question relating to the current thread, please do let us know and we will try out best to help you. In case if you have any other question on a different issue, we request you to open a new thread.

Thank you.