Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRealize Automation deployment in VMware Cloud Foundation fails with the error "Another VM with same name exists for VRA" (67767)

Last Updated: 4/23/2019Categories: InformationalTotal Views: 4258Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

vRealize Automation deployment in VMware Cloud Foundation fails with the error "Another VM with same name exists for VRA"

Not all vRealize Automation Windows VMs have joined Active Directory

The problematic VMs that didn't join Active Directory have the first 15 characters from their computer name identically the same.

Example:

LASP-vra01ias01, LASP-vra01ias02, and  LASP-vra01ias03

You see messages similar to the following in the /var/log/vmware/vcf/domainmanager/domainmanager.log file located on the SDDC Manager VM:

2019-02-28 01:46:37.463 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [      c.v.e.s.c.v.vrlcm.service.VrlcmServiceImpl]   Returned request progress details status = FAILED request ID = f4453537f394cc75582e9341bdb6b
2019-02-28 01:46:37.463 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   Persisting vRSLCM vRealize operation details in inventory.
2019-02-28 01:46:37.476 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRA deployment failed. vRSLCM Request state is FAILED.
2019-02-28 01:46:37.494 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRSLCM vRealize operation has failed. Error code is VRA_VM_GUEST_TOOLS_NOT_RUNNING.
vRSLCM exception message is Retries exhausted while checking if the VM  LASP-vra01ias01b has joined the domain.
vRSLCM error message is GuestTools not running

2019-02-28 01:47:04.609 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] INFO  [   c.v.e.s.c.client.vmware.vsphere.VcManagerBase]   HA feature on cluster LASP-VRAm01-mgmt01 is true
2019-02-28 01:47:04.612 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] WARN  [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase]   Shutting down the connection monitor.
2019-02-28 01:47:04.613 [vcf_dm,72db09a6e63488ca,6fe840f2755eba9b] [1-thread-6] ERROR [c.v.e.sddc.orchestrator.model.error.ErrorFactory]   [7TNFU6] VRA_VM_GUEST_TOOLS_NOT_RUNNING GuestTools not running.
com.vmware.evo.sddc.common.vrealize.vrslcm.error.reporting.exceptions.VrslcmOrchTaskException: GuestTools not running.

2019-02-28 01:57:19.141 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] INFO  [      c.v.e.s.c.v.vrlcm.service.VrlcmServiceImpl]   Returned request progress details status = FAILED request ID = f4453537f394cc75582e9341bdb6b
2019-02-28 01:57:19.141 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] INFO  [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   Persisting vRSLCM vRealize operation details in inventory.
2019-02-28 01:57:19.144 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRA deployment failed. vRSLCM Request state is FAILED.
2019-02-28 01:57:19.144 [vcf_dm,72db09a6e63488ca,53de211ae4e38d9e] [-thread-18] ERROR [c.vmware.evo.sddc.vrealize.vra.DeployVraContract]   vRSLCM vRealize operation has failed. Error code is VRA_VM_ALREADY_EXISTS.
vRSLCM error message is Another VM with same name exists for VRA

You see messages similar to the following in the /var/log/vlcm/vrlcm-server.log file located vRealize Suite Lifecycle Manager VM:

2019-02-28 01:42:21.976 ERROR [pool-2-thread-3] c.v.v.l.p.c.v.t.w.DeployIaasWindowsTemplateTask -  -- Exception while deploying windows template
com.vmware.vrealize.lcm.common.exception.vcenter.GuestToolsNotRunningException: Retries exhausted while checking if the VM  LASP-vra01ias01a has joined the domain

2019-02-28 01:47:30.328 INFO  [pool-2-thread-15] c.v.v.l.d.v.v.u.CoreUtility -  -- VM search name : LASP-vra01ias01a and Cluster is :LASP-VRAm01-mgmt01
2019-02-28 01:47:30.361 INFO  [pool-2-thread-15] c.v.v.l.d.v.v.u.CoreUtility -  -- VM Name  : LASP-vra01ias01a found for cluster: LASP-VRAm01-mgmt01
2019-02-28 01:47:30.361 ERROR [pool-2-thread-15] c.v.v.l.p.c.v.t.w.DeployIaasWindowsTemplateTask -  -- Exception while deploying windows template
com.vmware.vim.binding.vim.fault.DuplicateName: null

2019-02-28 01:47:30.361 INFO  [pool-2-thread-15] c.v.v.l.p.a.s.Task -  -- Injecting task failure event. Error Code : 'LCMVRACONFIG50004', Retry : 'true', Causing Properties : '{ CAUSE :: vmName ===  }'
com.vmware.vim.binding.vim.fault.DuplicateName: null

The vRealize Automation VMs that failed to join Domain show Event ID 2505 "Name conflict on the network" in the Event Viewer.

The Task Event on the Active Directory Domain Controller will show event ID 5722 . The event will occur When a computer is joined to a domain with a name that already exists.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This is  expected behavior due to a Microsoft limitation where NetBIOS names can only be 15 characters. For more information see Microsoft support article 909264

Resolution

Login to SDDC Manager UI. Navigate to Administration -> vRealize Suite -> vRealize Automation.

Click the Uninstall button.

Select a different naming convention for the vRealize Automation VMs, where the first 15 characters are not identically the same.

Generate new vRealize Automation Certificates for the  vRealize Automation VMs after changing their computer names.

Initiate a new vRealize Automation deployment.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
实际建立时，IPV6 BGP 邻居可能会在 NSX 3.x UI 上显示 "down"。这是表面问题 (80458)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.5.x

Take Our Survey

Support Assistant