Had an interesting issue the other week involving VMware Orchestrator. Workflows have been set up to use Configuration elements, and one of the attributes in the element was a VC:VmFolder. This would be set, but the workflow would fail, and when I went back to look at the attribute it was “not set”.

This had started happening after upgrading to vCenter 5, which includes Orchestrator by default. There was a relevant error in the logs:

ERROR

\[VimSession\]

getOrCreateVimObject() –> Cannot create com.vmware.vmo.plugin.vi4.model.VimVmFolder

Luckily the first link in a Google Search found the answer - - this was that the default vCenter plugin for vCO has an issue and needed to be updated.

After updating, the scheduled workflows complete without any problems … but the logs do still say “vi4” …