Quantcast
Channel: Azure Virtual Machines forum
Viewing all articles
Browse latest Browse all 12545

New-AzureVM : CurrentStorageAccountName is not accessible. Ensure the current storage account is accessible and in the same location or affinity group as your cloud service

$
0
0

Hello,

I'm trying to set up a new DC in my Azure cloud. At the moment I've already got one DC deployed, using a Virtual Network.

The virtual network is set to use that DC as DNS (and also the two DNS on my premise network).

So, if i'm adding a new VM on that VNet, the problem is that Azure set up dns improperly (I want my new DC to use itself as DNS Server).

The only way to have a different DNS config for a VM on a VNet is to use powershell. I'm using http://social.msdn.microsoft.com/Forums/windowsazure/en-us/a8b6c407-5a08-4b63-9b03-de9a8f4fd515/change-dns-servers?forum=WAVirtualMachinesVirtualNetwork as tutorial.

So I've already made a VM on the VNet, export the config, and then delete the VM.

But now I'm facing an issue I cannot understand. Everytime I'm trying to add my new VM using the xml config, I have the same error: 

New-AzureVM : CurrentStorageAccountName is not accessible. Ensure the current storage account is accessible and in the same location or affinity group as your cloud service.

I don't understand, as it's a new Service. I'm using the same affinity group as usual. What's wrong ?

regards,


Viewing all articles
Browse latest Browse all 12545

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>