Azure-Samples/MyDriving

.\deploy.ps1 "CentralUS" smhdinsight1234567 - always fails

shmisra opened this issue · 0 comments

shmisra commented

PS D:\IOT\MyDriving-master\scripts\PowerShell> .\deploy.ps1 "CentralUS" smhdinsight12345678

New-AzureRmResourceGroupDeployment : 5:12:46 PM - Error: Code=LocationNotAvailableForResourceType; Message=The provided location 'centralus' is not available for resource type
'Microsoft.DataFactory/dataFactories'. List of available regions for the resource type is 'westus,northeurope,eastus,westcentralus'.
At D:\IOT\MyDriving-master\scripts\PowerShell\deploy.ps1:147 char:16

  • ... ployment2 = New-AzureRmResourceGroupDeployment -Name "$DeploymentName ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotSpecified: (:) [New-AzureRmResourceGroupDeployment], Exception
    • FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

New-AzureRmResourceGroupDeployment : The deployment validation failed
At D:\IOT\MyDriving-master\scripts\PowerShell\deploy.ps1:147 char:16

  • ... ployment2 = New-AzureRmResourceGroupDeployment -Name "$DeploymentName ...
  •             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : CloseError: (:) [New-AzureRmResourceGroupDeployment], InvalidOperationException
    • FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

WARNING: Skipping the storage and database initialization...
D:\IOT\MyDriving-master\scripts\PowerShell\deploy.ps1 : At least one resource could not be provisioned successfully. Review the output above to correct any errors and then run the deployment script again.
At line:1 char:1

  • .\deploy.ps1 "CentralUS" smhdinsight12345678
  •   + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
  + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,deploy.ps1

For other regions that I tried, it always fails. Is there a new version of the PowerShell script that should process without any errors? Please clarify,