vCO vApp Upgrade Issue

So I decided to remediate my vCO vApp to the latest version, 4.2.1.  Everything went smooth after attaching the baseline that I created to upgrade it through VUM.  Upgrade looked successful, went to login and received:

Can’t connect to host…

After re-reading the release notes, I noticed the first Known Issue for Installation was:

After you upgrade the Orchestrator appliance to version 4.2.1, the Orchestrator server might not start automatically

So following the workaround provided I proceeded to:

    • Log in to the appliance home page.
    • Click Orchestrator Configuration, and log in.
    • Click the Database tab on the left, and click Update database.
    • Click the Startup Options tab on the left.
    • Click Start service.

This didn’t seem to resolve the issue for me.  I was still unable to login.  So what to do…I decided that I may need to clear all temporary files on the server.  You can do this by:

    • Log in to the appliance home page.
    • Click Orchestrator Configuration, and log in.
    • Click the Startup Options tab on the left.
    • Click Stop service.
    • Click the Troubleshooting tab on the left.
    • Click Clean directories.
    • Click the Startup Options tab on the left again.
    • Click Start service.

Viola!  This seem to resolve the issue I was having of logging in via the Orchestrator Client.

Related
The following two tabs change content below.

James Bowling

Principal Consultant - Data Center at General Datatech, LP
James Bowling is the creator of vSential.com. He currently works as the Principal of the Data Center Practice for General Datatech, LP (@GDTwire) in Dallas, TX. James is a VCAP5-DCD, VCAP5-DCA, VCP5-DCV/IaaS, VCP-Cloud, EMCCIS, EMCCA, vExpert (x4), Cisco Champion - Data Center (2013), PernixPro, and the Houston VMUG Leader. He is an avid golfer, bowler, DJ, Producer/Remixer, all-around good guy, and a Freemason.
One Response to vCO vApp Upgrade Issue
  1. [...] with the vCO service starting once the vApp has been rebooted post upgrade. To fix it, head on over here... professionalvmware.com/2012/04/orchestrator-use-vum-to-upgrade-the-vco-vapp

Leave a Reply