Troubleshooting: Installation and configuration

You can troubleshoot some of the problems that you might encounter when you are installing, configuring, or running HCL DevOps Test Integrations and APIs (Test Integrations and APIs).

Table 1. Troubleshooting **Test Integrations and APIs** installation and configuration issues
Problem	Description and Cause	Solution
Project fails to open - duplicate items	Each file within an Test Integrations and APIs 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 Test Integrations and APIs.	Test Integrations and APIs 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.
Test Integrations and APIs fails to start.	In some cases, the Test Integrations and APIs workspace can become corrupted.	Try to rename the .integrationtester folder and then restart Test Integrations and APIs.
Unix-like systems: program does nothing and exits.		In `Test Integrations and APIs 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 Test Integrations and APIs and Library Manager (`LibConfig`).
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 Test Integrations and APIs, you want to change the runtime language.		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. Test Integrations and APIs supports a subset of these language codes as documented in https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0078997 For example, if you want to display Test Integrations and APIs in Spanish, you use the following code: `-Duser.language=es_ES` For more information about using Library Manager, see Working with Library Manager. To use this language, restart Test Integrations and APIs.
After you configure an application in Library Manager one of the following events occur: Test Integrations and APIs fails to start. Test Integrations and APIs Agent fails to start if Test Integrations and APIs has started correctly. Both Test Integrations and APIs and Test Integrations and APIs 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 Test Virtualization Control Panel.	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.