Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
vSphere Client fails when adding the ESX/ESXi host to vCenter Server Appliance (2034504)
Symptoms
- When connecting an ESX/ESXi host to vCenter Server Appliance (VCSA), the vSphere Client fails
- In the /var/log/vmware/vpx/vpxd.log file, you see the error:
warning 'Default' opID=009D37BF-00000056] [VpxdMoHost::GetLinkedVmInt] Getting linked vm for vmid 2 on host <hostname> - COULD NOT FIND IT
Cause
Resolution
To resolve this issue, you need to consolidate the snapshots on the virtual machine that has too many snapshots.
To identify the virtual machine with too many snapshots and to consolidate the virtual machine:
- Connect to the ESX/ESXi host experiencing the issue using SSH.
- Run this command:
cd /etc/vmware/hostd
- Run this command to backup the vmInventory.xml file:
cp vmInventory.xml vmInventory.xml.SAFE
- Open the vmInventory.xml file using a text editor.
- Remove all entries within <ConfigRoot> and </ConfigRoot> tags.
- Run this command to restart the services:
/sbin/services.sh restart
- Reconnect the host to VCSA.
- Examine each virtual machine to identify the virtual machine with too many snapshots.
- Check the logs on the VCSA to identify the last virtual machine that was connected, which is probably causing the snapshot issue.
- Consolidate the snapshots on the virtual machine. For more information, see Consolidating snapshots (1007849).
- Rename the vmInventory.xml.SAFE file to vmInventory.xml.
- Reconnect the host to VCSA.
See Also
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

