Has anyone seen this message before? I just started getting in when I try to build machines at our California vCenter from our Dallas vCAC. This happens during the provisioning state and is caught on a "vim3WaitToolsStarted" Action. Is it timing out due to latency perhaps? It gets past building stage and the name is set fine.
Edit: I can build local machines just fine. It's only when building machines in California that I get this error.
Edit2: I'm noticing that VC:VirtualMachine is saying "Not Set" while the others such as vCAC:VirtualMachine show the vm name. The vim3Waittoolsstarted action requires VC:VirtualMachine. I have no idea why vCAC wouldn't pass this info for one set of machines vs. another??