Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

vMotion fails for a specific hosts. Migration fails with error message "The Object or item referred to could not be found" (68126)

Last Updated: 1/4/2024Categories: TroubleshootingTotal Views: 66172Language:
Chinese (Simplified)JapaneseEnglish

24 like this article

Subscribe to get an email
newsletter with new updates

24 people found this helpful Please provide article feedback:

Symptoms

Issue: Unable to vMotion virtual machines from specific Host. The migrations fails with error message "The Object or item referred to could not be found"

Purpose

To troubleshoot the migration of VM across the hosts. To resolve the issue of host vMotion and troubleshoot

Cause

Inside the vCenter, the Host is already part of cluster. When the customer adds the ESXi host into vDS and perform VM networking migration, all VM on that particular Host does not register on dVport correctly, The new port ID does not get assigned to VM network and it continues to use the old port ID  and network connection remains stable.

On the ESXi hosts you  will see  below error:

/var/log/hostd.log :

2019-05-14T03:21:53.272Z error hostd[2101236] [Originator@6876 sub=Hostsvc.NsxSpecTracker] Object not found/hostspec disabled

[LikewiseGetDomainJoinInfo:354] QueryInformation(): ERROR_FILE_NOT_FOUND (2/0):

2019-05-14T03:22:23.275Z error hostd[2100948] [Originator@6876 sub=Hostsvc.NsxSpecTracker] Object not found/hostspec disabled

2019-05-14T03:18:52.472Z info hostd[2101544] [Originator@6876 sub=Solo.Vmomi opID=2f09d043-7f00 user=vpxuser] Result:

--> (vim.fault.PlatformConfigFault) {

--> faultCause = (vmodl.MethodFault) null,

--> faultMessage = (vmodl.LocalizableMessage) [

--> (vmodl.LocalizableMessage) {

--> key = "com.vmware.esx.hostctl.default",

--> arg = (vmodl.KeyAnyValue) [

--> (vmodl.KeyAnyValue) {

--> key = "reason",

--> value = "Unable to delete DVPort "" that is in use, use list: TCE-VMWSO01.eth0"

--> }

--> ],

--> message = <unset>

--> }

--> ],

--> text = ""

--> msg = ""

--> }

Impact / Risks

No Impact to VMs connection, only migration fails with error message.

Resolution

There are two solutions :

1) You need to Power Off Virtual Machine and  Unregister  it.Then register the virtual machine again and migrate. You may try creating a new test-VM or deploy a test-VM from template or Clone existing VM to test-VM

OR

2) Open the vCenter server UI and login with an administrator account.

Select the respective dVSwitch  , => right click select "Add and Manage Hosts" => Manage Host Networking

Select the problematic Host ( Check Box )

Skip to "Migrate VM networking". Check the box "Migrate virtual machine networking" to see the VMs on the host.

Select "Configure per virtual machine". The list of VMs should show you the current port group under one of the columns.

Click on "Assign Port Group". It will display a list of Port Groups on the dVSwitch. Select a port group to assign the VM to. If possible, reassign the same port group it was already using. If not possible, assign a different port group. (Assigning a different port group could cause the VM to lose connectivity until you reassign it back.)

Click "Next" then "Finish"

Assigning the same port group will  re-registration of network port ID of the VM and you should be able to Migrate the VM after this process.

During the network re-registration,  the VM will loose the network for few seconds based on network traffic at that point of time.

You may validate by clicking the dVSwitch => Configure => Settings => Topology. The UI should show you " Port Group"  and the VM connection should show you "Green " visible connection to uplinks

We recommend you to try this on non-critical VM and after success you may try on critical-production VM.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

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 vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant