Mike's Realm chown -R us ./base

15Dec/110

vCenter Orchestrator Trouble: Server service fails to start – service terminated with service-specific error Incorrect function

I was setting up a new instance of Orchestrator inside my lab and came across this issue.  the Orchestrator Server service would not start, andi nside the vCenter Orchestrator Configuration webpage, we don't have any output in the log--so we investigate the Windows logs...

In the system log all you see is Error: The VMware vCenter Orchestrator Server service terminated with service-specific error Incorrect function..

Poking around we come across a log file @ C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.log which sheds some light on the problem:

Your first thought might be disk space, did a log run away? No that isn't the case--Java Heap refers to memory, looking inside the wrapper.conf from the command above we find more information.

Java has to allocate 2Gb of RAM on startup. My VM only had 1.5Gb, that looks like the issue--this is what you get for ignoring the Minimum System Requirements (assuming your running Orchestrator on same server as your vCenter).  Increase the RAM on your VM and this error should be gone. vCenter Server should have a minimum of 3Gb of RAM.

Share
Comments (0) Trackbacks (0)

No comments yet.


Leave a comment

No trackbacks yet.