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
This error happens because the deployment scripts functionality might not be available when the region launches. However, retrying the replication process after a short interval should fix the issue.
58
81
59
82
**SQL Virtual Machine registration error**
60
83
61
84
When migrating a Virtual Machine with SQL Server, if you select the option to register with the SQL Virtual Machine resource provider, you encounter the following error:
62
85
63
-
The virtual machine couldn't be registered with the SQL Virtual Machine Resource Provider. Azure error message: `'No registered resource provider found for `<newregion>` and API version '2017-03-01-preview' for type 'Locations/registerSqlVmCandidate`.
86
+
The virtual machine couldn't be registered with the SQL Virtual Machine Resource Provider. Azure error message: No registered resource provider found for `<new region>` and API version '2017-03-01-preview' for type 'Locations/registerSqlVmCandidate`.
- Australia Central, Australia Central2, Australia East, Australia South East
102
+
- Brazil South
103
+
- Canada Central, Canada East,
104
+
- Central India
105
+
- Central US
106
+
- East Asia
107
+
- East US, East US2
108
+
- France Central, France South
109
+
- Germany West Central
110
+
- Israel Central
111
+
- Italy North
112
+
- Japan East, Japan West
113
+
- Jio India West
114
+
- Korea Central, Korea South
115
+
- Mexico Central
116
+
- North Central US
117
+
- North Europe
118
+
- Norway East
119
+
- Poland Central
120
+
- Qatar Central
121
+
- South Africa North,
122
+
- South Central US
123
+
- South India,
124
+
- South East Asia,
125
+
- Spain Central
126
+
- Sweden Central
127
+
- Switzerland North
128
+
- UAE Central, UAE North
129
+
- UK South, UK West
130
+
- West Central US
131
+
- West Europe
132
+
- West India
133
+
- West US, West US2, West US3.
84
134
85
135
> [!NOTE]
86
136
> Despite this error, the Virtual Machine migration succeeds. However, users must know that the Virtual Machine won't be registered with the SQL Virtual Machine Resource Provider in the specified region.
0 commit comments