vCenter Service stops responding and reports error: "Double register of key: 'DynamicTypeManager-XXX' and name: ''

Products

• VMware vCenter Server
• VMware vCenter Server 6.0
• VMware vCenter Server 7.0
• VMware vCenter Server 8.0

Issue/Introduction

• vCenter service fails to start
• In vpxd.log file, you see log entries similar to:

YYYY-MM-DDT09:50:43.610-07:00 error vpxd[09980] [Originator@6876 sub=Vmomi] [VpxVmomi] Double register of key: 'DynamicTypeManager-10' and name: ''
YYYY-MM-DDT09:51:25.954-07:00 info vpxd[09980] [Originator@6876 sub=Default] CoreDump: Writing minidump
YYYY-MM-DDT09:51:33.730-07:00 panic vpxd[09980] [Originator@6876 sub=Default] 
--> 
--> Panic: NOT_REACHED bora\vpx\common\vpxVmomi.cpp:850
--> 
--> Backtrace:
--> [backtrace begin] product: VMware VirtualCenter, version: 6.5.0, build: build-8024368, tag: vpxd, cpu: x86_64, os: windows, buildType: release
--> backtrace[00] vmacore.dll[0x001F342A]
--> backtrace[01] vmacore.dll[0x000682D0]
--> backtrace[02] vmacore.dll[0x0006A79E]
--> backtrace[03] vmacore.dll[0x00224A07]
--> backtrace[04] vmacore.dll[0x00224BD1]
--> backtrace[05] vmacore.dll[0x00033FBD]
--> backtrace[06] vmacore.dll[0x00033FEC]
--> backtrace[07] vpxd.exe[0x01221ED0]
--> backtrace[08] MSVCR120.dll[0x00066920]
--> backtrace[09] MSVCR120.dll[0x0005E36D]
--> backtrace[10] ntdll.dll[0x0006BAF3]
--> backtrace[11] vpxd.exe[0x000CFCC6]
--> backtrace[12] vpxd.exe[0x002F7E44]
--> backtrace[13] vpxd.exe[0x002BDC02]
--> backtrace[14] vpxd.exe[0x001A5ABC]
--> backtrace[15] vpxd.exe[0x001C9164]
--> backtrace[16] vpxd.exe[0x00236D4B]
--> backtrace[17] vpxd.exe[0x0023A3EB]
--> backtrace[18] vpxd.exe[0x00485357]
--> backtrace[19] vpxd.exe[0x00485BA7]
--> backtrace[20] vpxd.exe[0x01185893]
--> backtrace[21] kernel32.dll[0x000159CD]
--> backtrace[22] ntdll.dll[0x0005383D]
--> [backtrace end]


Note: The preceding log excerpts are only examples. Date, time, and environmental variables will vary depending on your environment.

Environment

VMware vSphere 6.x
VMware vSphere 7.x
VMware vSphere 8.x

Resolution

Please contact Broadcom Support to resolve this issue and reference this KB article.