Overview

Insight Agent might fail starting up when configured as a Windows service and launched with Launcher.exe -i Launcher.conf, with the below error in the logs.

STATUS | wrapper | YYYY/MM/DD hh:mm:ss | Insight Agent installed.
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | --> Wrapper Started as Service
STATUS | wrapper | YYYY/MM/DD hh:mm:ss | Launching a JVM...
FATAL | wrapper | YYYY/MM/DD hh:mm:ss | Unable to execute Java command. The system cannot find the file specified. (0x2)
FATAL | wrapper | YYYY/MM/DD hh:mm:ss | "java" -Djava.library.path="." "-Djava.util.logging.SimpleFormatter.format=%1$tY/%1$tm/%1$td %1$tT.%1$tL %4$-6s %5$s%6$s%n" "-Dlauncher.appdir=../" "-Dlauncher.working=..//working" "-Dsun.net.inetaddr.ttl=30" -classpath "launcher-client.jar;wrapper.jar" -Dwrapper.key="9874uihUIY83Ah3kfky" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.pid=1264 -Dwrapper.version="3.2.3" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp com.actional.launcher.client.Start
FATAL | wrapper | YYYY/MM/DD hh:mm:ss | Critical error: wait for JVM process failed

This happens even if Java is available on the environment variable path.

Solution

Add the parameter wrapper.java.command in launcher.conf file with the path of the java binary eg., wrapper.java.command = C:\Insight\jre\bin\java.exe

Testing

Once the configuration is updated as shown, Insight Agent should start as a Windows service.