ESX host shows as not responding in vCenter Server when performing any activity
search cancel

ESX host shows as not responding in vCenter Server when performing any activity


Article ID: 309600


Updated On:


VMware vCenter Server


  • When any task is performed on any ESX host in a cluster, the host shows as Not Responding in VirtualCenter/vCenter Server (even though there are no network issues between the ESX host vCenter Server)
  • The VPXD logs contain numerous error messages similar to:

    [2008-07-10 14:35:17.706 'App' 3672 error] [VpxdVmomi] Invalid login on host <host name>
    [2008-07-10 14:35:27.722 'App' 2308 error] [VpxdVmomi] Invalid login on host <host name>

  • You see backtraces in the VPXD logs similar to:

    backtrace[01] eip 0x01176caa ?CreateBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@z
    backtrace[02] eip 0x0115192e ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z
    backtrace[03] eip 0x014a1509 (no symbol)
    backtrace[04] eip 0x014d8b81
    backtrace[05] eip 0x014d8d48 ?UnsetNoRxLoss@PipeBackingInfo@VirtualSerialPort@Device@Vm@Vim@@QAEXXZ
    backtrace[06] eip 0x014daf48 ?Throw@InvalidLocale@Fault@Vim@@UAEXXZ
    backtrace[07] eip 0x014daf7f ?Throw@InvalidLogin@Fault@Vim@@UAEXXZ


VMware VirtualCenter 2.5.x
VMware VirtualCenter 2.0.x
VMware vCenter Server 4.0.x


This issue occurs when vCenter Server cannot log in to one of the ESX hosts in the cluster, causing a VPXD core dump.
To resolve this issue, refresh the vCenter Server Inventory:
  1. In the vCenter Server Inventory, right-click on the host causing the error message in the VPXD logs and select Remove.

    Note: When the ESX host is removed from the inventory, all performance data is lost.

  2. Re-add the ESX host to the vCenter Server Inventory.

Additional Information

For related informatio, see Diagnosing an ESX or ESXi host that is Disconnected or Not Responding in vCenter Server (1003409).Troubleshooting an ESXi/ESX host in non responding state