«

»

vCenter Orchestrator client won’t start – java security issue

This will be just a simple blog post about how to get passed a potential Java security issue/problem when you want to start the vCenter Orchestrator (vCO) client.

This is verified for the following infrastructure:

  • Windows Server 2008 R2
  • Java version 7 update 51
  • vCenter orchestrator 5.5

My customer tried to start the Orchestrator client from the vCO home page, https://fqdn:8281/vco/

Screen Shot 2014-02-12 at 09.31.53

When starting the vCO client my customer received the following error:

Screen Shot 2014-02-11 at 23.33.55

By clicking the details button we found the following error “Missing required Permission manifest attribute in main jar”

Screen Shot 2014-02-11 at 23.34.09

This means we should add the vCO FQDN including the port in the Security section of the Java Control Panel found in the Windows Server Control Panel.

Screen Shot 2014-02-12 at 09.54.10

When starting the vCO client once more it launches as expected.

Screen Shot 2014-02-11 at 23.38.42

1 ping

  1. Newsletter: June 7, 2014 | Notes from MWhite

    […] Orchestrator Client won’t start – Java security issue I am sharing this to help you solve a potential vCO and Java issue.Β  However, I have seen this exact issue with the […]

Comments have been disabled.