Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Modernization Workbench / Enterprise Analyzer Failure when parsing Java files

Modernization Workbench / Enterprise Analyzer Failure when parsing Java files

Problem:

When trying to parse a Java program with Enterprise Analyzer it reports the following error:

            JavaParser                                failure   Failed to start parser process

Resolution:

To have been able to load the Java files into the product, the java add-on must have been installed on the machine they were loaded on, but the parsing may take place on another machine, so the following should be checked.

  1. The Java-Add has been installed on the machine. This can be seen from ‘Programs and Features’ from the Control Panel.
    1. For Modernization Workbench (MW) installations, it is called  Modernization Workbench Java Add-on
    2. For Enterprise Analyzer (EA) installations, it is called Micro Focus Enterprise Analyzer Java Add-on
    3. If neither of these are present, then you need to install the Java Add-on product that is supplied with your installation media.

  2. That Java 5.0 (1.5) or higher is installed on the machine. If Java is not present on the machine then this can be downloaded from java.com or your preferred java supplier.
  3. As a minimum, the Java Runtime (JRE) must have been installed on the machine.  MW and EA will work with the Java Development Environment (JDK), Java Standard Edition (JSE) and the Java 2 Platform Enterprise Edition (J2EE). MW / EA requires the 32bit version of Java to be installed to work correctly.
    1. For Pre-Java 7 installations on 64-bit machines, check Programs and Features from the Control Panel and ensure that there is both the 64bit and 32-bit version of your Java product installed.
    2. Java 7 does not show a separate 32bit and 64bit program, so just ensure that Java 7 is installed.
    3. If the JRE is not present, then this can be downloaded from java.com or your preferred java supplier.

  4. Check that the 32bit Java runtime is available. This is done via a Dos command prompt. You may have to change directory to relevant java bin directory. Then try the following:
    1. java  -version -d32
    2. That should display the Java version. If it displays the an error similar to this ‘Error: This Java instance does not support a 32-bit JVM.‘ then you only have the 64-bit version of Java and will need to install the 32-bit version.
    3. If the 32-bit Java product is not present, then this can be downloaded from java.com or your preferred java supplier

  5. The user preferences within the workspace may not be set to the correct location of your 32-bit product.
    1. This is selected from Options > User Preferences > Path to JRE folder
      1. For MW this needs to point to the JRE directory eg c:\Program Files (x86)\Java\jdk1.7.0_05\jre
      2. For EA this can point to either the JRE or JDK directory, so c:\Program Files (x86)\Java\jdk1.7.0_05 is correct
    2. The MW / EA product uses the rt.jar file to parse Java programs. The product needs to be able to locate this file and it is typically in the the c:\Program Files (x86)\Java\jdk1.7.0_05\jre\lib directory. The product needs should be told the location of Java so that it can locate the correct rt.jar file.
    3. If Java is installed on the machine and the rt.jar file is not present, then this indicates an incorrect or corrupted Java installation and Java should be re-installed

  6. Check the installation of the Eclipse Toolkit that is part of the MW / EA product. This is found in the eclipse31 directory under the MW / EA installation directory. 
    1. For MW the default location is: C:\Program Files (x86)\Micro Focus\ Modernization Workbench\eclipse31
    2. For EA the default location is: C:\Program Files (x86)\Micro Focus\Enterprise Analyzer\eclipse31
    3. From the eclipse31 directory, run eclipse.exe, this should display the eclipse31 splash screen and ask you to select a project. If this does happen, then you can cancel the workspace load as eclipse31 is installed correctly and working.
    4. If eclipse does not start and displays an error screen then check:
    5. - Your path statement. 32-bit Java needs to appear before 64-bit Java, this may require changing the order that Java appears on your path.
    6. - Your MW / EA installation. It may have become corrupted. In this case you need to re-install MW / EA.

After trying all of these steps, if Java files are still not parsing, then please raise a support incident so that it can be investigated and this can then be updated with your scenario.

Incident #2614948

 

 

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-03-26 06:25
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.