We are also seeing these errors after upgrading to vCenter server 6.0 U2 (build 3634793). Looks like there is a KB article about it.
The fix is to upgrade to vCenter 6.0 U3
We are also seeing these errors after upgrading to vCenter server 6.0 U2 (build 3634793). Looks like there is a KB article about it.
The fix is to upgrade to vCenter 6.0 U3