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.
50
58
51
59
**SQL Virtual Machine registration error**
52
60
53
61
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:
54
62
55
-
The virtual machine couldn't be registered with the SQL Virtual Machine Resource Provider. Azure error message: 'No registered resource provider found for location '' and API version '2017-03-01-preview' for type 'Locations/registerSqlVmCandidate'. The supported api-versions are '2017-03-01-preview, 2021-11-01-preview, 2022-02-01-preview, 2022-02-01, 2022-07-01-preview, 2022-08-01-preview, 2023-01-01-preview, 2023-10-01'. The supported locations are 'australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, canadaeast, centralindia, centralus, eastasia, eastus, eastus2, francecentral, francesouth, germanywestcentral, israelcentral, italynorth, japaneast, japanwest, jioindiawest, koreacentral, koreasouth, mexicocentral, northcentralus, northeurope, norwayeast, polandcentral, qatarcentral, southafricanorth, southcentralus, southindia, southeastasia, spaincentral, swedencentral, switzerlandnorth, uaecentral, uaenorth, uksouth, ukwest, westcentralus, westeurope, westindia, westus, westus2, westus3'.
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`.
> 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