Miscellaneous Troubleshooting

This topic describes troubleshooting issues that are either common to several areas or belong to an area separate from server configuration, Web Navigator, or Studio Modeling Native Apps.

This page discusses:

See Also
Implementation Troubleshooting
ENOVIA Studio Modeling Platform Troubleshooting

Laptop Performance

Problem

From a laptop computer, opening ENOVIA Web pages, setting context and performing finds seem to take longer than should be necessary.

Solution

Check the following:

  1. Set your browser default page to a local file instead of the browser's default homepage of www.microsoft.com or http://www.mozilla.org. Browser initialization and host name resolution as well as anything using TCP/IP will all perform faster.
  2. Check that the hostname for the DNS settings is set to the machine's network name.
  3. Open the Network option from the Control Panel.
  4. Click the Protocols tab and choose TCP/IP protocol properties.
  5. Click the DNS tab and make sure the host field specifies the correct machine network name.

Open the \winnt\system32\drivers\etc\hosts file. Make sure your machine IP and name are listed. This helps resolve the host name more quickly.

Session Timed Out Error

Problem

The following error is received when performing any operation: java.lang.Exception: Session timed out

Solution

Timeout limits are set and enforced in the Web or app server. If a period of inactivity occurs that is greater than the limit set, for security reasons, users are forced to login again. Consult your Web server's documentation for information on setting this limit.

Tar Error When Unpacking Distributions

If you receive LongLink error(s) when attempting to untar an ENOVIA distribution file such as ENOVIALiveCollaborationServer-VERSION.tar, install GNU tar 1.14 or higher and unpack with gtar. The original POSIX format can only handle 100 characters for link names.

Problems with JSP Path for ENOVIA apps

If you have problems with the path for the JSPs when using an ENOVIA app, make sure the following settings are defined as follows in the web.xml file. 

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