Today I found a strange problem in a VMWare infrastructure I manage: the connection to the V irtualCenter Server was unstable using both the desktop client and the new webclient.
When I connected to the server that runs the VMware VirtualCenter Server service, I noticed that the service kept restarting. In the Windows’ System event registry I found several errors as follows:
The log folder (C:\ProgramData\VMware\VMware VirtualCenter\Logs) contained some crash dump files (.dmp) – in blue – in addition to the log files – in red:
I opened the latest log file and searched for Writing minidump finding the following line:
[05600 info 'Default' opID=SWI-66a88c0e testSet=host-100,vm-277] CoreDump: Writing minidump
some rows below, the process (05600) that failed logged the reason:
[05600 panic 'Default' opID=SWI-66a88c0e testSet=host-100,vm-277] --> --> Panic: Assert Failed: "controllerType != 0" @ d:/build/ob/bora-1378903/bora/vim/lib/vmvalidate/configOptionValidate.cpp:558
The error explains that the vm-277 has a wrong configuration parameter (controllerType): while parsing its configuration, the VirtualCenter Server crashed.
In the log file I also found the name of the VM:
Initializing min EVC key for VM TESTBLOGIC03 [vim.VirtualMachine:vm-277]
I connected directly to the ESXi host where the VM was running and I shut it down, resolving the problem.