The VMware vRealize Orchestrator service starts but then stops with the error: An essential server component is missing or invalid, the server will be shutdown
search cancel

The VMware vRealize Orchestrator service starts but then stops with the error: An essential server component is missing or invalid, the server will be shutdown

book

Article ID: 342981

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • When you start the VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) service, it runs for a moment and then stops
  • In the VMware vRealize Orchestrator server.log file, you see entries similar to:

    An essential server component is missing or invalid, the server will be shutdown

  • In the VMware vRealize Orchestrator server catalina.out log file, you see entries similar to:

    ERROR {} [ServerChecker] Server integrity problem: interface com.vmware.o11n.licensing.
    LicenseAttributes is not visible from class loader java.lang.IllegalArgumentException: interface com.vmware.o11n.licensing.
    LicenseAttributes is not visible from class loader


Environment

VMware vCenter Orchestrator Appliance 5.1.x
VMware vCenter Orchestrator Appliance 5.5.x

Cause

This issue occurs due to a problem accessing the embedded database after the VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) disk becomes full, or by another server failure while using the embedded database or internal PostgresDB.

Resolution

This is a known issue affecting VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) Appliance 5.1.x.

Currently, there is no resolution.
Running VMware vRealize Orchestrator with internal or embedded databases is only supported for testing purposes. Use an external database if your VMware vRealize Orchestrator is in a production environment.

If you are using the embedded database, work around this issue by performing these steps:
  1. Set up a new VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) appliance and configure it with the same plug-in and configuration as your original system.
  2. Copy the database files from Orchestrator_install_DIR/app-server/data, on the old VMware vRealize Orchestrator server to Orchestrator_install_DIR/app-server/data on the new VMware vRealize Orchestrator server.
  3. Copy all files and folders beginning with internal.hsqldb.*.
  4. Verify the permissions for all the files copied that are set to owner/group of VMware vRealize Orchestrator.
  5. Restart the VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) server.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.