Installation Troubleshooting

Errors during app login from the emxLogin page such as:

java.lang.ClassNotFoundException: java.lang.Exception: Message:Compile error: 
/usr/tmp/851aa48/emxPropertyUtil_mxJPOHXUH8QAAAAEAAAAB.java:21: cannot access java.lang.Object 
bad class file: /usr/JDK_VERSION/jre/lib/rt.jar(java/lang/Object.class) 
class file has wrong version 49.0, should be 48.0

This exception usually this means that the JPO's were compiled on a higher version of the JDK and the class files are attempting to be used by a lower version of jdk.

All JPOs and JSPs should be compiled with the same version of the JDK as the app server will use. If you use the BPS Admin tool to run the MQL compile command, this will ensure that the same JDK is used.

Also make sure that the MX_CLASSPATH and PATH information in mxEnv.sh file are pointing to the correct JDK, and verify that the app server is indeed picking up this JDK when running in RIP mode. Also check the JAVA_HOME variable in your environment.

Problems accessing the login or home page

Make sure web.xml has the correct login and home page properties, which by default are as follows:

ematrix.home.page=/ematrix/emxHome.jsp

On the app pages, you see tags for strings instead of appropriate onscreen text

Make sure all StringResource.properties files are in STAGING/ematrix/properties/ and that the classpath statements are correct for the Web server (see the next remedy below).

Install error:

#0  System Error #1900014  
Cannot open file 'c:matrixVERCoreAppsFrameworkCommonCommonCompatibilityCheck.tcl'

Be sure that MQL is not in "escape" mode. Run the following MQL command to determine whether escaping is enabled (you must log in as a Business Administrator to do so):

MQL<> print escape;

If the system indicates that escape mode is on, turn it off before running the install with:

MQL<> set escape off;

Refer to "Working with Workspace Objects" in the MQL Concepts.

Install errors that indicate an administration object couldn't be installed because it was not unique or an administration object couldn't be renamed because an object already exists with that name.

A custom administration object may have been registered with the same symbolic name as an object being installed/renamed. For example, you may have registered administrative objects that you expect to be included in the framework or you may have registered an object that coincidentally has the same properties as a framework object.

To correct the problem so the installation proceeds correctly, you need to unregister the added schema that is causing the collisions. To unregister schema, use the eService Change Administration Property wizard, as described in the 3DEXPERIENCE Basics. Note that there is no need to unregister added schema if it is not causing a collision with installing schema.

After installing the framework, you can either use the framework's object or your custom object. Either way, you'll probably have to make changes to the one you use to include code and other characteristics from the one you don't use. For considerations on which object to use and instructions, see the "When There are Similarities Between the Framework and Your Database" section of the 3DEXPERIENCE Basics.

Do not register schema that you anticipate to be in an upcoming release of the framework without explicit permission from Framework Engineering They must provide you with the registration information.

Web server errors regarding problems finding classes

The app server startup scripts that need matrix .jar files don't refer to .jar files directly. Instead they call ComputedClassPath. This only requires that you have a valid connection (bootstrap) file in place and that all the directories that contain the .jar files you need are listed in MX_CLASSPATH. You should only need to configure this if you have customapps or custom JPOs with non-Matrix dependencies.