It seems that even just starting a VM while vCenter is down could trigger it. I think the issue happens if the VM config was modified in some way while vCenter was down. I've seen the issue several times already, unfortunately, and it's not limited exclusively to USB devices. ( vMAN: which is fine if you know which VM is causing the issue but this is not obvious from the logs / errors without going into the DB - IMO)

You might need to repeat this process if the failure happens again. Workaround from VMware: Unregister the problematic virtual machine from the host inventory and restart the vCenter Server. If you face this issue in PROD and are not willing to try the fix below just contact VMware Support for help. UPDATE : This issue has been patched with vCenter 6.5b, just search for ' pk_vpx_vm_virtual_device '. As I couldn't find anything relevant to this issue I thought I would do a simple write up about it for anyone is interested / experiences the problem. has anyone experienced this one before on other versions?Īfter some investigation I linked this back to the “Host USB Device” and I managed to solve my problem. I asked DR google and couldn't really find anything specific to “pk_vpx_vm_virtual_device”.

Error: Error (-1) “ODBC error: (23505) – ERROR: duplicate key value violates unique constraint “pk_vpx_vm_virtual_device' 'An unrecoverable problem has occurred, stopping the VMware VirtualCenter service.

The second the properties loaded in the webgui, vCenter would shutdown with the following error: I manually recovered the failed VM's onto another host, once all VM's were back online the vCenter started to crash as soon as I tried to view the properties of a specific VM (via the Webclient) which was also on that original failed host. My vCenter 6.5 server was running on a host which experienced a failure. Just wanted to share an issue I had and get feedback if anyone has experienced this.

Vcenter 6.5 keygen