Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

Provision request failed: A server error was encountered. Error requesting machine. Machine name [servername] already exists.

$
0
0

VCAC 6.0.1.1


After deploying a Windows 2012 R2 server from a basic blueprint request, it immediately fails with a "machine name already exists" error.  This is a very basic out-of-the-box request workflow with no customization other than a hostname property specified to override the prefix.


The vCAC log viewer indicates:

Source: Repository

Instance Name: Repository

Message: Error requesting machine. Inner Exception: Exception has been thrown by the target of an invocation. Base Exception: Machine name [myactualservername] already exists.

 

VMware KB 2043297 indicates that this is caused by a pre-deployment check of AD, DNS, or WINS.  To resolve, verify that the machine name does not exist in AD, DNS, or WINS.

 

My question is, are there any other logs I can check to find out what is causing this failure to trigger?  Is it AD, DNS or WINS?  I do not have WINS implemented in this environment, AD does not have a computer account with this server's name, and I have tried with or without DNS entries with the same result.  (We tend to pre-provision DNS A and PTR records in our IPAM solution prior to deploying the VM with other requests working just fine).  It seems to me that vCAC has a record of this machine name, but not any of the components mentioned in the KB article.  Has anyone ran into this? 

 

Thank you,

 

James


Viewing all articles
Browse latest Browse all 9859

Trending Articles