Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Issues with vCenter Orchestrator plug-in for vCenter Server 5.0.1.1 (2032840)

Details

After you install the vCenter Orchestrator plug-in for vCenter Server 5.0.1.1 you may experience some problems with the property collector such as that the properties for an object cannot be loaded if the Inventory Service is stopped or missing.

Another problem which might occur is slow performance with the Inventory Service. If you start several workflows that are waiting for vCenter Server tasks completion, the Orchestrator server and client become very slow until all vCenter Server tasks complete.

Solution

To resolve the problem with the property collector, you can restart the Inventory Service. This workaround is applicable only if you have migrated to vSphere 5.0 and later.

To resolve both problems, upgrade the plug-in with the vCenter Server 5.0.1.2 plug-in, posted in the Orchestrator communities at http://communities.vmware.com/docs/DOC-19851.
  1. Download the .vmoapp file from the communities Web site http://communities.vmware.com/docs/DOC-19851.
  2. Log in to the Orchestrator configuration interface as vmware.
  3. On the General tab, click Install Application.
  4. Upload the vCenter Server plug-in.
    a) Click the magnifying glass icon.
    b) Select the .vmoapp file to install.
    c) Click Open.
    d) Click Install.
    The vCenter Server 5.0.1.2 plug-in replaces the previous installation of the plug-in.
  5. On the Startup Options tab, click Restart service to complete the plug-in installation.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: