Skip to main content

Dependency error message displayed in vLCM cluster managed by Images when saving/validating an Image of VMware Tools 6.x component to vSphere 7.0 (or higher version)

 

Symptoms
  • Dependency error messages are displayed in vLCM cluster managed by Images, when user tries to save/validate an Image by adding <VMware Tools release version>-6.x component to vSphere 7.0 or higher version.
  • An sample of the error you may experience is as below:
Component TOOLS-20200618 has VIBs that obsolete each other.
            Remove component TOOLS-20200618 as it contains VIBs that obsolete each other.
            Component TOOLS-20200618 has unmet dependency esx-version = 6.0.0 that is not provided by any component in depot.
            Problem with component TOOLS-20200618 could not be resolved.
            Component TOOLS-20200618 has unmet dependency esx-version = 6.5.0 that is not provided by any component in depot.
            Problem with component TOOLS-20200618 could not be resolved.
Cause
  • <VMware Tools release version>-6.x component is intended to be used only with vSphere releases 6.x.
Resolution
Remove <VMware Tools release version>-6.x component from the Image. vSphere 7.0 (or higher) contains a higher version of the VMTools component than <VMTools release version>-6.x, and supports feature set of <VMTools release version>-6.x

Comments

Post a Comment

Popular posts from this blog

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...
Post a Comment
Read more