You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I'm trying to launch the deploy from the setup document using ARM.
Testing deploying both in West Europe and North Europe. Suffix is pietrobr.
I get always failed deploy with a conflict "Error" on the Azure Synapse workspace.
If I look at activity log
Operation name
Create or Update Workspaces.
Time stamp
Wed Dec 09 2020 18:16:48 GMT+0100 (Central European Standard Time)
Event initiated by
-----@-----
Error code
ResourceOperationFailure
Message
The resource operation completed with terminal provisioning state 'Failed'.
If I manually create an Azure Synapse Analytics on my subscription it works just fine.
====
Update: if I don't change any parameters of the template for deployment (setting only the prefix), the deployment seems to complete successfully.
I guess it could be a problem with SQL Pool password, that I changed in my first run with the region.
I will do some more tests tomorrow.
Any ideas?
The text was updated successfully, but these errors were encountered:
Since you are using the pietrobr suffix, it's plausible you are getting resource naming conflicts. Can you please confirm the problem persists if you are using some different, random suffix?
Hi I'm trying to launch the deploy from the setup document using ARM.
Testing deploying both in West Europe and North Europe. Suffix is pietrobr.
I get always failed deploy with a conflict "Error" on the Azure Synapse workspace.
If I look at activity log
Operation name
Create or Update Workspaces.
Time stamp
Wed Dec 09 2020 18:16:48 GMT+0100 (Central European Standard Time)
Event initiated by
-----@-----
Error code
ResourceOperationFailure
Message
The resource operation completed with terminal provisioning state 'Failed'.
If I manually create an Azure Synapse Analytics on my subscription it works just fine.
====
Update: if I don't change any parameters of the template for deployment (setting only the prefix), the deployment seems to complete successfully.
I guess it could be a problem with SQL Pool password, that I changed in my first run with the region.
I will do some more tests tomorrow.
Any ideas?
The text was updated successfully, but these errors were encountered: