Copy data assistant stuck at spinning icon

[pr1ngl3]

Hi,

I am trying to use the copy data assistant to build a pipeline to copy across a SQL DB.  When selecting the 'copy data assistant' option, it just sits at a loading type screen with a spinning icon as per the below. It never finishes or errors out, just sits there.

Does anyone have any ideas?

[rfosha]

Hi, having the exact same issue. Cleared cache and recreated the workspace several times and it did not help.

[Anonymous]

Hi @pr1ngl3 ,

First of all, in Data Factory, the Choose data source itself takes some time to load.

I have Data Factory open as well, but I am able to display the Choose data source screen normally.

So I think you can reopen the interface and try again. Of course you can also open it through another channel.

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[pr1ngl3]

Hi and thanks for the reply.

I have tried both ways of opening copy data assistant to no avail. I have also sat with 2 other users, one of whom can open it and the other get sthe same issue as me.

[Anonymous]

Hi  @pr1ngl3 ,

Have you solved your problem? If so, can you share your solution here and mark the correct answer as a standard answer to help other members find it faster? Thank you very much for your kind cooperation!

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @pr1ngl3 ,

Can I ask if you have resolved your issue now?

It does seem to be a frustrating issue that normally does show up. As you also mentioned your other coworker he was able to open it.

So I think you can switch computers to use or clean up the cash and do it again. Of course you can also create a new workspace and do it again.

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi. I was having the same issue and I solved it by cleaning the Cache from my browser.
Hope this can help you.

[pr1ngl3]

Hi, unfortunately not, clearing the cache has not fixed the issue.