question

arkiboys avatar image
0 Votes"
arkiboys asked PRADEEPCHEEKATLA-MSFT commented

Workspace validation output on publish

When trying to publish, I get this error:
Publish fails: Default linked services cannot be changed. Please revert changes in the default linked service

my current settings is shown in screen-shot below:
124638-image.png




I searched on line for this issue, I found out that it appears the solution is:
to disconnect from git, delete the workspace_publish branch and then reconnect to git.

Question:
Do you think the above is the solution and if so, can I get guidance on how to do this as I am concerned in-case I loose any of the work.

Thank you

azure-synapse-analytics
image.png (6.8 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

KranthiPakala-MSFT avatar image
0 Votes"
KranthiPakala-MSFT answered PRADEEPCHEEKATLA-MSFT commented

Hi @arkiboys,

Thanks for using Microsoft Q&A forum and posting your query.

Yes, the above solution is suggested for this issue by product team and if you want to make sure that your workspace_publish data can to restored, you can clone it or create a backup of that branch by renaming it to some other name as shown in below sample:

125111-image.png

  1. Disconnect the Git repository from Synapse
    125010-image.png

  2. Delete the workspace_publish branch in that repository or clone it with a different name as backup

  3. Reconfigure Synapse with the same repository

Here is another thread from past where a similar issue was discussed: Publish fails: Default linked services cannot be changed. Please revert changes in the default linked service

You will be able to restore all the code that is committed to your main or collaboration branch.

But as a best practice I would highly recommend to take a backup of the branch before deleting so that if something is unusual you can always revert back.


Hope this info helps.



  • Please accept an answer and up-vote if it helps. Original posters help the community find answers faster by identifying the correct answer. Here is how.

  • Want a reminder to come back and check responses? Here is how to subscribe to a notification.





image.png (340.3 KiB)
image.png (296.4 KiB)
· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
The workspace_publish looks to be empty because we have not published before.
based on that, shall I just go ahead and disconnect as you suggested but without the clone bit?
Thank you

0 Votes 0 ·

Hi @arkiboys, Thanks for getting back.
Yes, please follow those steps and do let us if you see any issues.

One thing I would like to check is, have you committed the development changes to main branch (which is nothing but collaboration branch)?

0 Votes 0 ·
arkiboys avatar image arkiboys KranthiPakala-MSFT ·

Hi,
Yes, the pipeline changes are always being merged into main branch by using pull request.

I see in DevOps that there is nothing in workspace_publish, probably because we have not done publish yet.
On another note, We do have blob storage which we use too.
I will disconnect from workspace_publish as you suggested and then I guess our pipelines should continue to work as normal?
but then if I want to publish, what do I do?
Thank you

0 Votes 0 ·
Show more comments

Hello,
I did not get round to following your instructions, however, I am looking into this in more detail...
To confirm, as mentioned before, the workspace_publish branch looks to be empty (See below) which is probably because I have not been able to publish before
127861-image.png


The main branch does have a-lot of objects because I create PR and always merge to the main branch (See below)
127720-image.png


The Azure DevOps Repository is as follows (See screen-shot)
127854-image.png



Based on your suggestions to get rid of the error when I try to publish, should I do the following steps?
1-
click on disconnect in the Git Repository under the management tab
2-
Then reconnect to Azure DevOps Repository?

Question:
I can go ahead with the disconnect but not familiar from that point onwards when I have to remove the workspace_publish and then Connect ? Can you elaborate the steps for these please?
Thank you

0 Votes 0 ·
image.png (13.8 KiB)
image.png (17.3 KiB)
image.png (7.0 KiB)

Hi @arkiboys,

As suggest by @KranthiPakala-MSFT, you can just disconnect the Git repository, then delete the workspace_publish branch in that repository or clone it with a different name as and then reconfigure Synapse with the same repository.

For more details, refer to Switch to a different Git repository

Hope this helps. Do let us know if you any further queries.

0 Votes 0 ·