CA NFA Harvester service will not start NFA 9.1(Windows)


Article ID: 49079


Updated On:


CA Network Flow Analysis (NetQos / NFA)



"CA NFA Harvester service" will not start in NFA 9.1.x as well as some other some other services like "CA NFA Poller", "CA NFA Harvester File Pump Web Service", "CA NFA Harvester Data Retention Service", "CA NFA DNS/SNMP Proxies", "CA NFA Collection and Poller Webservices", and the "CA Performance Center SSO" service on the NFA console server, may also Fail to start to start.

The service will fail to start with the error: "Error 1067: The process terminated unexpectedly."


The "harvester-wrapper.log from \CA\NFA\Netflow\Logs will show errors like the ones below:

 	FATAL | wrapper | 2012/12/13 10:02:05 | Critical error: wait for JVM process failed 	 	STATUS | wrapper | 2012/12/13 10:07:47 | --> Wrapper Started as Service 	 	STATUS | wrapper | 2012/12/13 10:07:47 | Java Service Wrapper Standard Edition 64-bit 3.5.7 	 	STATUS | wrapper | 2012/12/13 10:07:47 | Copyright (C) 1999-2010 Tanuki Software, Ltd. All Rights Reserved. 	 	STATUS | wrapper | 2012/12/13 10:07:47 | 	 	STATUS | wrapper | 2012/12/13 10:07:47 | Licensed to CA Technologies for NFA Harvester Service 	 	STATUS | wrapper | 2012/12/13 10:07:47 | 	 	STATUS | wrapper | 2012/12/13 10:07:47 | Launching a JVM... 	 	FATAL | wrapper | 2012/12/13 10:07:47 | Unable to execute Java command. The system cannot find the file specified. (0x2) 	 	FATAL | wrapper | 2012/12/13 10:07:47 | "java" -Dfile.encoding=Cp1252 -Duser.language=en -Xms128m -Xmx264m     -Djava.library.path="../lib" -classpath 	    "../bin/;../lib/wrapper.jar;../conf;../lib/commons-dbcp-1.4.jar;../lib/commons-pool-1.5.6.jar" 	    -Dwrapper.key="-v-LFnAmLazAUEmy0048LaysbaWCUhkc" -Dwrapper.port=32002 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 	    -Dwrapper.disable_console_input="TRUE" -Dwrapper.version="3.5.7-st" -Dwrapper.native_library="wrapper"     -Dwrapper.service="TRUE" 	-Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 -Dwrapper.lang.domain=wrapper     org.tanukisoftware.wrapper.WrapperSimpleApp 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | -------------------------------------------------------------------- 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | Advice: 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | Usually when the Wrapper fails to start the JVM process, it is 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | because of a problem with the value of the configured Java command. 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | Currently: 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | Please make sure that the PATH or any other referenced environment 	 	ADVICE | wrapper | 2012/12/13 10:07:47 | variables are correctly defined for the current environment. 

This issue can occur if Java is not installed, or the Jave jre*\bin directory is not in the PATH system environment variable on the server. Java can be installed with or without updating the System PATH variable.


Component: NQRACO


  1. Verify Java Runtime Engine (JRE) 1.6 or later is installed in Add/Remove Programs

  2. Check the System Path variable and verify that the Java jre*\bin directory is in the PATH system variable.

    For example if you Java is installed to "C:\Program Files (x86)\Java\jre7\bin" on your server, you should have in the PATH variable.

    To Check this you can simply type "PATH" from any command prompt and it will show you what is set in the path.

    Also you can right click "Computer->Properties" then select "Advanced system settings" then click the "Advanced" tab if not already set, then "Environment Variables".

    Under the "System Variables" windows, select and edit the PATH variable and check for the jre*\bin directory.

  3. If not present add the path to your Java\Jre*\bin directory, for example if Java is installed to "C:\Program Files (x86)\Java\jre7\bin" after the last entry in the path preceded by a semi colon as shown below.

  4. Once the PATH is updated correctly, you can verify by opening a new command prompt and running the command "java -version" and see if it returns the version of Java or if it errors. If it shows the version you should be ready to start services at this point.

  5. Attempt to start services and verify they all can now start. (Note some may have already started themselves as soon as the change was made, in some cases you may need to reboot the server for the evnrionment variable changes to take effect)


1558721278258000049079_sktwi1f5rjvs16w02.gif get_app
1558721276331000049079_sktwi1f5rjvs16w01.gif get_app
1558721274376000049079_sktwi1f5rjvs16w00.gif get_app