|Applies To||Affected Versions: 3.6.X; 3.5.X; 3.0.X|
|Resolution||The Aveksa Remote Agent Service fails to start on the target PC with the following error "Could not start the AveksaAgent service on Local Computer. Error 1067: The process terminated unexpectedly". Aveksa Agent Installer does not setting JAVA_HOME variable correctly.|
There are several causes for this error:
Case 1: JRE not installed
On systems that do NOT have Java Version 1.5 and higher installed, the Aveksa Agent installer installs JRE Versions 1.4 or Version 1.5 based on user input. After installing the selected JRE the Aveksa Agent installer does NOT create the environment variable JAVA_HOME which is required by the Aveksa Agent Service. Due to this, the Aveksa Agent Service fails to start.
In order to get the service to start, set a system wide environment called JAVA_HOME and point it to the root of the JRE that you want the Aveksa Agent to use after installing the Aveksa Agent. For example, JAVA_HOME=c:\Program Files\Aveksa\bin\jre1.5_07.
Case 2: Old JRE installed:
This problem also manifests in the case where the customer has Java 1.5 installed but chooses to use Aveksa supplied JRE 1.4 since the customer wants to use this remote agent to host a WebLogic Collector. In this case, since the Aveksa Agent does not appropriately set the JAVA_HOME variable used by the Aveksa Agent Service, the Aveksa Agent Service will continue to use Java 1.5 causing a compatibility issue with the WebLogic collector.
In order for the agent to use the correct JRE, set a system wide environment called AVEKSA_JAVA_HOME and point it to the root of the JRE that you want the Aveksa Agent to use after installing the Aveksa Agent. For example, AVEKSA_JAVA_HOME=c:\Program Files\Aveksa\bin\jre1.4. Open the wrapper.conf file in <Aveksa_Install_Root>\conf\wrapper.conf and modify the line "wrapper.java.command=%JAVA_HOME%/bin/java" to wrapper.java.command=%AVEKSA_JAVA_HOME%/bin/java