org.eclipse.equinox.launcher errors occur when logging into the WebSphere Lombardi Edition (WLE) Authoring Environment

Diagnosing The Problem

The issue happens when WebSphere Lombardi Edition Authoring Environment is installed under a path that contains non-Latin and non-numeric characters. That includes some European and most Asian characters.

WebSphere Lombardi Edition Authoring Environment is built on Eclipse and uses a path to one of the components as a system variable. Eclipse converts that path to characters from the first part of the ASCII code page and, as a result, this situation breaks the path for those languages that are not compatible with the ASCII code page.

The following scenarios are possible:

• A message box is displayed with Java Virtual Machine Launcher in the header and some part of the path is replaced with '???' symbols. This situation means that the path contains characters from codepages that are not enabled or supported on your system. This situation might happen if you have copied the entire WebSphere Lombardi Edition Authoring Environment directory from a workstation that supported the exact codepage to a workstation that does not support it.
• A message box is displayed with Java Virtual Machine Launcher in the header and some part of the path is replaced with similar Latin symbols - like 'č' replaced with 'c', 'ä' with 'a' and so on.This situatuation happens when the exact codepage is supported and enabled on your system, but it is not set as the default system codepage.
• A message box is displayed with "Teamworks 7" in the header and refers to the workspace log file. The log file contains java.lang.UnsatisfiedLinkError message deeply under org.eclipse.equinox.launcher.Main.* calls. This situation happens when the exact codepage is supported and enabled on your system and is set as the default system codepage.