book
Article ID: 344538
calendar_today
Updated On:
Environment
VMware VirtualCenter 2.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.1.x
VMware VirtualCenter 2.5.x
VMware vCenter Server 4.0.x
VMware vCenter Server 5.5.x
Cause
This issue can occur if the ESX/ESXi host or a virtual machine is in an unexpected state.
Resolution
To work around the issue, perform
one of these options:
-
Cancel any existing task from the VMware Infrastructure Client.
-
Wait until any pending tasks are complete.
- Restart the VMware vCenter Server service.
-
Disconnect and reconnect the host to the vCenter Server.