VPXD stops responding and reports error: "Double register of key: 'vm-XXX' and name: ''
search cancel

VPXD stops responding and reports error: "Double register of key: 'vm-XXX' and name: ''

book

Article ID: 318920

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

  • Unable to start the vCenter service.
  • In the vpxd.log file, you see log entries similar to:
YYYY-MM-DDTHH:MM:SS error vpxd[06912] [Originator@6876 sub=Vmomi] [VpxVmomi] Double register of key: 'vm-XXX' and name: ''
YYYY-MM-DDTHH:MM:SS warning vpxd[06456] [Originator@6876 sub=VpxProfiler opID=UpdateSCMStatus-?] UpdateSCMStatus [TotalTime] took YYYY ms
YYYY-MM-DDTHH:MM:SS warning vpxd[06764] [Originator@6876 sub=VpxProfiler opID=UpdateSCMStatus-?] UpdateSCMStatus [TotalTime] took YYYY ms
YYYY-MM-DDTHH:MM:SS info vpxd[06912] [Originator@6876 sub=Default] CoreDump: Writing minidump
YYYY-MM-DDTHH:MM:SS panic vpxd[06912] [Originator@6876 sub=Default] 
--> 
--> Panic: NOT_REACHED bora\vpx\common\vpxVmomi.cpp:###
--> 
--> Backtrace:
--> 
--> [backtrace begin] product: VMware VirtualCenter, version: 6.0.0, build: build-4541947, tag: vpxd
--> backtrace[00] vmacore.dll
--> backtrace[01] vmacore.dll
--> backtrace[02] vmacore.dll
--> backtrace[03] vmacore.dll
--> backtrace[04] vmacore.dll
--> backtrace[05] vmacore.dll
--> backtrace[06] vpxd.exe
--> backtrace[07] MSVCR90.dll
--> backtrace[08] MSVCR90.dll
--> backtrace[09] ntdll.dll
--> backtrace[10] vpxd.exe
--> backtrace[11] vpxd.exe
--> backtrace[12] vpxd.exe
--> backtrace[13] vpxd.exe
--> backtrace[14] vpxd.exe
--> backtrace[15] vpxd.exe
--> backtrace[16] sechost.dll
--> backtrace[17] KERNEL32.DLL
--> backtrace[18] ntdll.dll
--> [backtrace end]

Notes:

  • For more information on the log file, see Location of vCenter Server log files
  • The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.



Environment

VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.5.x

Resolution


This issue is resolved in VMware vCenter Server 6.5 Update 2.