Skeetneet
Contributor
Contributor

I've been struggling with this issue for two weeks when upgrading to U2A build 4541947, and finally support came through with a solution.

In our case, the cause was vCenter JRE not being updated correctly.

To workaround the issue, remove the contents of the jre and then perform the upgrade.

Steps:

  1. Stop all vCenter services.
  2. Take a backup of jre folder located at C:\Program Files\VMware\vCenter Server\
  3. Empty the contents of  jre folder except for the below files :

C:\Program Files\VMware\vCenter Server\jre\bin\libvecsjni.dll

C:\Program Files\VMware\\vCenter Server\jre\lib\ext\vmware-endpoint-certificate-store.jar

  1. Perform an upgrade to vCenter Server Update 2a.