This needs to be fixed. I have been working with support on this one, and per their instructions we have had the latest bits of Reporter installed. Still we would see the vcenter not connected error. The VC is a physical blade with a lot of resources.
What I hae also observed is while collection is on going, in the hosts and clusters view with VC selected on left and the hosts tab selected on right, we would lose the CPU summary value of one or more hosts. Then it would come back. Someone owes us an explanation as the solution was sold and we are not able to utilize it completely due to the above reasons.