Installing the newest version of vCAC in a lab, I ran into an issue I thought only I would encounter - turns out a peer ran into the very same issue a couple of days later so I thought I would post the problem and solution.
In our case we were both installing an new (as yet unreleased) version of vCAC with a separate SQL server for the IaaS database component. The IaaS Windows server and SQL server were cloned from the same base image. By the way, this issue isn't related to vCAC or a particular version - you could really see this with other products. It's a known issue with MSDTC and VM clones.
The installation of the IaaS component goes fine, you can even configure the tenant, add fabric groups, vSphere end points, business groups - but then things get weird. You will likely see that in your vSphere reservation, the memory, storage and network are basically empty - like nothing has been collected. In fact, if you go and look at the collection status for the compute resource you will see that the Inventory and State collections are not even showing up as configured (neither "on" nor "off").
Finally, you will see these type of entries in the IaaS vCAC server log (also can see this in the vCAC UI under Infrastructure > Monitoring > Log) -