I posted a reply to your other thread in this same community...
Perhaps you should move that other thread to a vCenter community and we keep this one for the vCO issue... I'll paste my reply here to keep the vCO discussion in one thread:
Yes, it seems you have two separate issues here- 1 with your vCenter (I can't help there) and 1 possibly with vCO... I would focus first on the vCenter issue and get that resolved before spending much time on the vCO issue as vCenter is certainly more critical to get resolved.
As for the vCO side though:
- Make sure the services are stopped
- In vCenter Orchestrator Configuration, go to the Troubleshooting tab of the navigation pane
- Click the link to "Cancel workflow runs" <- if you have any workflows running, caught in loops, etc, they will ALL be stopped the next time vCO successfully starts up
- Click the link to "Clean directories" <- this will cleanup the temporary deployment folders on the vCO server
- Click the link to "Reset current version" <- this will force the re-installation of the plug-ins that are installed and enabled
- Go to the vCenter Server tab of the navigation pane
- Edit and DISABLE your host(s) <- this is just a temporary step for troubleshooting purposes
Ensure your vCO Server has a MINIMUM of 3GB of RAM allocated to it (4GB is recommended). Anything less and you risk adverse effects such as services not starting properly.
Now, attempt to start your vCenter Orchestrator Server service from the "Startup Options" tab of the navigation pane.