azure - The cloud service you have chosen is deployed in a region or affinity group that does not currently support virtual machines -
problem:
i attempting add new vm second domain contoller existing domain , error when attempting add same cloud service.
steps1:
created virtual network
assigned affinity group network (cloudag)
scripted creation of vm following protocol add dc dns.
as part of process cloud service created vm (dccloudservice) in affinity group.
scripted creation of second vm , when attempting related same cloud service using line:
$service = 'dccloudservice'
(please note have amended other parameters , 100% sure command value causing conflict error)
error1:
the following error displayed:
new-azurevm : "an exception occurred when calling servicemanagement api. http status code: 409. service management error code: conflicterror. message: specified dns name taken.. operation tracking id: 121129c1212be49c8be9f81411178a61ac." @ line:25 char:1 + new-azurevm -servicename $service -affinitygroup $ag -vms $myvm1 -dnssettings $m ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + categoryinfo : closeerror: (:) [new-azurevm], servicemanagementclientexception + fullyqualifiederrorid : microsoft.windowsazure.management.servicemanagement.iaas.persistentvms.newazurevmcommand
steps2:
so using azure mgt portal try create same vm. when selecting existing dc cloud service name receive message:
error2:
"the cloud service have chosen deployed in region or affinity group not support virtual machines"
following step 7 in article:
"step 7 - add second domain controller"
it suggests:
"what creates virtual machine in existing cloud service can added availability group later".
question:
simply put, powershell ise , azure mgt portal not allow me add new vm existing cloud service , cannot understand why.
thank help.
edited add region north europe.
29/07/13 edited add response tabrez:
thank reply. hope detail below helps explain.
1) vnet created within last month in north europe. access specific sub 25/06/13.
2) script used domain joining new vm. works add node domain if create new cloud serice value. if use existing dc cloud service value dns error explained above.
$mydns = new-azuredns -name 'mydns' -ipaddress '172.16.0.4'
$image = 'windows-server-2012-datacenter-201305.01-en.us-127gb.vhd'
$service = 'clouddc1'
$ag = 'cloudag'
$vnet = 'cloudvnet'
$pwd = 'password'
$size = 'small'
$vmname = 'dc2' $myvm1 = new-azurevmconfig -name $vmname -instancesize $size -imagename $image | add-azureprovisioningconfig -windowsdomain -password $pwd -domain 'domain' ->domainpassword 'password' -domainusername 'adminuser' -joindomain 'domain.com'| set-azuresubnet -subnetnames 'back'
new-azurevm -servicename $service -affinitygroup $ag -vms $myvm1 -dnssettings $mydns -vnetname $vnet
3) q. there many articles adding first dc vnet using powershell , why important make value $mydns = 127.0.0.1. when using domain join add additional dc same domain must enter first dc ip address $mydns value domain join successful.
if using 127.0.0.1 cannot find domain.
if use 172.16.0.4 $mydns value additional dc , dc1 fails additional dc (dc2) surly has problem resoling dns queries ?
no info on net explaining how add second domain controller / additional domain controller / backup domain controller / replica domain controller on azure addresses $mydns issues important creating first dc dns correctly using 127.0.0.1 loopback ip.
please note vnet has following dns server ips
172.16.0.4 (dc1). 172.16.0.5 (dc2) once created. 8.8.8.8 google1 8.8.8.4 google2 192.168.1.3 (site site vpn dc2) 192.168.1.1 (site site vpn dc1)
site site vpn down key keeps changing if dont use cisco or juniper routers. need install isa server maintain connection.
it looks ps you're attempting create new cloud service second vm has same dns name 1 you've created. can share exact call new-azurevm can take look?
for issues you're having deploying vm through management portal, if you've confirmed you've selected same cloud service in deployed first vm, you'll need open support ticket take closer @ subscription. error message you're seeing typically shows when user creates affinity group before region supported virtual machines. if you've started following tutorial , created affinity group in past few days, or weeks, not culprit.
Comments
Post a Comment