Troubleshooting

For each error message listed below, possible causes and suggested corrections are provided.

Updating Message

Possible causes:

• The user does not have sufficient privileges to make changes to the installation directory during a p2 update.

Suggested corrections:

• Give the user full control of installation directory.
• Reinstall to a directory outside of Program Files.
• Upgrade to the most recent version of Workbench for Eclipse.

Dependency Message

Cannot complete the install because of a conflicting dependencyPossible causes:

• The user does not have sufficient privileges to make changes to the installation directory during a p2 update.
• The version being upgraded to is not compatible with a p2repo update.

Suggested corrections:

• Give the user full control of installation directory.
• Reinstall to a directory outside of Program Files.
• Upgrade to the most recent version of Workbench for Eclipse.

Version Check Messages

Invalid Response to Version Check (Return Code 789)Possible causes:

• JCL error. The return code 789 means the CSS TP was unable to obtain the version check information.

Suggested corrections:

• The STASK statement in the HCI parmlib member (default HCI00) is not specified, or it specifies the wrong PROC name.
• The PROC does not exist in a PROCLIB scanned by the system.
• The PROC has JCL errors and will not start.
• The STEPLIB DD of the PROC is not set up with the proper HCI, CSS, and File-AID libraries.
• The STEPLIB DD libraries are not APF-authorized.
• Security issues caused the PROC not to start. All datasets defined in this PROC (STEPLIB) must either have (a) universal read access (UACC READ) or (b) the PROC must be defined to a started-task security group that has READ access to all of these datasets.
• If there are no Data Editor/File-AID functions to be used, such as iStrobe only plug-in installed, this message is displayed as a warning message ‘only’ meaning Data Editor is not accessible.
• If the CXSS* Started Task PROC was updated, to make changes to the Proc, HCI must be recycled.

Possible causes and correction:

• For AFC2 users, the CXSSTC started task ID needs to have a GSO definition in the STC table to allow it to start jobs with a dynamic name.

Silent Install Message

NullPointerException during silent installPossible causes:

• The installation directory structure was not preserved when copied from the install media.

Suggested corrections:

• Re-copy the installation setup program, preserving the parent directory structure \Topaz\Windows\Disk1\InstData\VM

Features Missing or do not Load after Upgrade

Occasionally, after an upgrade of Workbench for Eclipse or the plugins (in an Eclipse instance) using the Check for Updates method, features will appear missing or do not load.

Possible causes:

• - Certain Topaz or Eclipse bundles have started up out of order or did not reload.

Suggested corrections:

• - Create a shortcut to topaz.exe or eclipse.exe, found in the eclipse folder in the install location. In the Properties of the shortcut add -clean at the end of the path in the Target field. Restart Workbench for Eclipse or Eclipse instance using the shortcut.
• - Add the -clean option to the topaz.ini or eclipse.ini file found in the eclipse folder in the install location. Restart Workbench for Eclipse or Eclipse instance. After the initial restart, the-clean option can be removed from the file.