I have the same issue. Deployed via suite lifecycle manager 1.3. The only thing I can really find is time being out of sync, but my 2x vra appliances and vrb have the same time server and time zones set.
Could you please confirm where you see this error ?
Is it on VRBC , or vrops ?
Because I delta with a situation where in it was the problem with wrong vrops plugin from vcenter mob page .
Removed older version of plugin and re-registered vcenter , after which data collection went smooth,
Could you check if you see a older vrops plugin in vcenter mob page , if yes then remove it --> re-register Vcenter instance from vrops -->post this perform data collection and check if this gives you this error again.
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
I'm pretty sure that the problem, in my case, is because the last version of vRB is not compatible with the last version of vROps.
I'm waiting for the new version to confirm.
Mine is integrated into vRA 7.4. It is failing the vRA and vCenter data gathering with the same error. I checked the data collector logs and it just gives me the same error, so I'm not sure where to investigate further.
Just got off the phone with support and evidently it boils down to the time zone being set. Evidently the appliance requires it stay on UTC. And changing back to UTC once it's been changed requires editing the database.
He pointed me to this article: VMware Knowledge Base
I'm going to redploy just because it's a fairly fresh install and just won't touch the time zone this time!