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/
When starting the vCO client my customer received the following error:
By clicking the details button we found the following error “Missing required Permission manifest attribute in main jar”
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.
When starting the vCO client once more it launches as expected.
1 pings
Newsletter: June 7, 2014 | Notes from MWhite
June 7, 2014 at 11:47 pm (UTC 0) Link to this comment
[…] 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 […]