Troubleshooting: Installation and configuration

You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL OneTest™ API.

Table 1. Troubleshooting HCL OneTest™ API installation and configuration issues
Problem Description and Cause Solution

Project fails to open - duplicate items

Each file within an HCL OneTest™ API project has a unique identifier of the following format:editableResource createdTimestamp="1317292623890" createdUser="atester" id="-44ea417a:132b496f2c1:-7e17" type="test_resource"

This problem is caused by project files that are copied by using the operating system rather than copying within HCL OneTest™ API.

HCL OneTest™ API must always be used to copy objects.

The error message lists which files have the same IDs and the solution is to remove one of them and reopen the project.

HCL OneTest™ API fails to start.

In some cases, the HCL OneTest™ API workspace can become corrupted.

Try to rename the .integrationtester folder and then restart HCL OneTest™ API.

Unix-like systems: program does nothing and exits.

In HCL OneTest™ API Installation Directory\configuration, check for log files with the file name format UTC timestamp.log (for example, 1253866725028.log). A new log file is created for each execution of HCL OneTest™ API and Library Manager (LibConfig). You can send any applicable files to IBM Support if you are unable to solve the problem.

Linux™ systems: fail to start - java.lang.UnsatisfiedLinkError

If the following error occurs, you need to install the libXtst package:


java.lang.UnsatisfiedLinkError: /home/root/jdk1.6.0_16/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory

Contact your system administrator for assistance.

After you install the latest version of HCL OneTest™ API, you want to change the runtime language.
  1. Run the Library Manager and add the following entry on a separate line in the JVM Arguments field on the Application page of Library Manager: 
    -Duser.language=<Java language>

    For a list of language codes, see JDK 7 and JRE 7 Supported Locales. HCL OneTest™ API supports a subset of these language codes as documented at Software Product Compatability Translation Reports.

    For example, if you want to display HCL OneTest™ API in Spanish, you use the following code: 
    -Duser.language=es_ES

    For more information about using Library Manager, see Working with Library Manager.

  2. To use this language, restart HCL OneTest™ API.
After you configure an application in Library Manager one of the following events occur:
  • HCL OneTest™ API fails to start.
  • HCL OneTest™ API Agent fails to start if HCL OneTest™ API has started correctly.
  • Both HCL OneTest™ API and HCL OneTest™ API Agent fail to start.
This problem occurs in any of the following conditions:
  • When JVM arguments for any application are added to Library Manager in the following instances:
    • For a new version of the application
    • For the second time to the same version of the application

    The cause can be that the same JVM arguments are already added when the application was configured the first time or for a previous version of the application.

  • When any of the JVM arguments added to Library Manager are invalid.
Perform any of the following actions:
  • When you add JVM arguments to Library Manager, you must change the dependent parameters or use different values for the parameters in the arguments.

    For example, you must set a different port from the port that is already set either in the previous version of the application or set during the previous installation of the application.

  • Enter valid JVM arguments to Library Manager.

Stubs that are created for Resource Monitoring do not start in HCL Quality Server.
This problem occurs in any of the following conditions:
  • This problem occurs when you add the same JVM arguments for Resource Monitoring to Library Manager in the following instances:
    • For a new version of the application
    • For the second time to the same version of the application
  • When any of the JVM arguments added to Library Manager are invalid.
Perform any of the following actions:
  • When you add the JVM arguments to Library Manager for Resource Monitoring, you must change the dependent parameters or use different values for the parameters in the arguments.

    For example, you must set a different port from the port that is already set either in the previous version of the application or set during the previous installation of the application.

  • Enter valid JVM arguments to Library Manager.