This looks like a known intermittent issue for environments that are running with vSAN. We do have a bug for tracking this for a future release. At the moment, the only workaround we can offer is to follow the user's guide instructions for manually running the reporter.
i guess i just solved these error messages temporarily or permanently,
by migrating the two vmmark3-template(originally located in SUT vsandatastore) to iSCSI1 storage(the third shared storage).
i had remembered that before these error messages popped up, i did re-configure and re-build the iSCSI storage server once.
despite the storage name still set to the same(iscsi0 and iscsi1).
maybe this is a cause of the error messsages?
however, i still couldn't generate the scores manually by command perl ../../tools/tilescore.pl
(had to skip almost ever workloads to acquire an incomplete graph.html)
To generate the scores manually for a Turbo run, you should use "tilescore.pl -x 1800"