Issue with Synapse Link connection (properly set services) due to unexplained error message

Question

I have following issue: I have properly set Azure SQL database link service and also Dedicated SQL pool for connecting Synapse with Azure SQL. I have tested connection and it passed. But cannot finish the creation and start the linked connection, as it show something wrong with a connection (its test has successfuly passed in another dialog) I have set the Azure SQL Database linked service

But when I click on the button "Test connection" (on the right of the AzureSQLDatabase combo box), not in the dialogue above, it returns an error - it is obvious that it is not testing anything behind the scenes, as it returns the Error message right away (not waiting few tenths of seconds as usually when awaiting response). When I click on it, there is nothing, just the blank popup window with no explanation:

Then in the next step, when I try to Start the Linked Connection, it returns finally this:

Do you, please, have and idea, what do I miss here? It is really hard to guess what is wrong when the error message window just stays silent...

Answer 1

Hi Thanks for reaching out to Microsoft Q&A. Strange! This doesn't even seem to pass the initial steps to consider any error from data factory. Did the connection is really without any issues? Did you try refreshing the browser page or performing the same from new browser window? If you still receive the same error, I would suggest to open a new microsoft support request. Please Upvote and Accept as answer if the reply was helpful, this will be helpful to other community members.

Answer 2

Hello Peter Ševčík,

Thanks for the details. I get the same blank screen when I click on the test connection from the left side.

But I don't see this as an issue while replicating the tables/data.

You should be able to publish the new link connection. The error message you previously saw is related to a different link connection saved in the workspace.

You need to either delete the linkconnection7 or fix the targetlinkedservice.

This should fix the issue.

I hope this helps. Please let me know if you have any further questions.