Installation Process Issues

Installation Has Failed

This error occurs when multiple installation processes are started. Sometimes, unzipping Setup.exe takes more than usual time due to the system specifications or some other technical problems. Users are requested to wait for some time once they double-clicked Setup.exe.

Solution:

If you face the error mentioned above, close the dialogue box and double-click Setup.exe again.

Incompatible Client Server Version

This next-generation installer handles all server and client related updates easily. Users are requested to apply updates whenever made available by team Qualitia to maintain server-client compatibility.

Solution:

If you face this error, please apply the latest update available for Qualitia Server.

Other Issues

Execution Report Not Getting Generated

You may find execution reports are not getting generated after the suite execution is completed. At times, some of the Windows policies block Qualitia registering few Qualitia components. This may result in not generating results for the Suite executions.

In order to resolve this issue, you must update the Windows registry based as mentioned below:

Press Win+R to summon the Run dialog box.
Type regedit and press Enter.
In Windows 7 and Windows Vista, click the Yes or Continue button or type the administrator's password.
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy registry.
Set the value as 0 as mentioned in the screenshot below.
Close Registry.

This driver is not configured for integrated authentication.

This error occurs when using Qualitia with SQL server 2016 developer edition and the Authentication Mode is set as Windows Authentication.

Solution:

Download Microsoft JDBC Driver 6.0 for SQL Server.
Unzip the file at some temporary location.
Go to enu > Auth.
Copy the dll depending on your OS (32 or 64-bit) version.
If you are using 32-bit, then copy sqljdbc_auth.dll from x86 folder and if you are using 64-bit, then copy sqljdbc_auth.dll from x64 folder.
Open the Java directory that is set under Configuration Settings > Execution > Java Install Path.
Add the dll file to lib and bin folders.
If you are using jre7:
1. Go to enu > jre7.
2. Copy sqljdbc41 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib].
If you are using jre8:
1. Go to enu > jre8.
2. Copy sqljdbc42 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib].

Qualitia Configuration File does not exist, can you please save Qualitia Configuration.

This issue occurs when the configuration file is missing. The file is created when you save the configuration settings for the first time.

Solution:

Log on to Qualitia Automation Studio.
On the Settings menu, click Configuration Settings.
Click Save.

Incompatible .Net Framework: Method not found: '!!0[] System.Array.Empty()'

This issue occurs when .Net framework installed is not compatible.

Qualitia Automation Studio requires minimum .Net Framework 4.6.2 installed in the system where client is being installed.

Solution:

If you face the error mentioned above, close the dialogue box and upgrade the .Net Framework to 4.6.2. Refer to the Prerequisites and Configurations section for more information.

Cloning Machines with Qualitia Installation is Not Supported

Some organizations follow a practice of creating Virtual Machines (VM) with standard configurations and then clone it for different users to use. If they install Qualitia on the base image, Qualitia licensing manager may get duplicate installation id for the cloned VM. In all likelihood, the end user may receive a licensing error. It is, therefore, recommended to install Qualitia separately on the VMs after they are cloned.

When trying to log in into Qualitia, the user may get the following error [when the machine is cloned with Qualitia Installation].

Qualitia License Key Not Found. (H0007)

Solution:

In case you come across this error:

Ensure that the license server is up and running.
Verify that the Sentinel LDK License Manager service is started. (To open Windows services console; press Windows R and then enter Services.msc)
Restart the Sentinel LDK License Manager service using Windows services console.

If the issue still persists, follow the steps mentioned below:

Create a file with its name in the following format - hasp_108764.ini
Open this file using notepad and add the following setting in it:
SERVERADDR = IP address of the license manager system.
For Example: If your license manager system’s IP address is 192.168.1.1 then setting will be: SERVERADDR = 192.168.1.1
For Windows 7 and later versions, copy the hasp_108764.ini file to the following location: %localAppData%/SafeNet Sentinel/Sentinel LDK/
Note: If not present, manually create folders SafeNet Sentinel/Sentinel LDK.
Open the url http://localhost:1947 and go to Configuration > Access to Remote License Manager, select all check boxes, add required information and then click Submit.
Go to Windows services console (Press Windows R and enter services.msc to open Windows Services console).
Select the service Sentinel LDK License Manager and restart it.
You should be able to launch Qualitia with license being acquired from the remote license manager.
For Verification if the license has been recognized by the license server, open the Sentinel ACC portal (http://localhost:1947) and click session to view the licenses acquired by various systems.

You can now log on to Qualitia Client without any error.

Unable to Execute Offline Package

Qualitia automatically registers all the binaries to system registry during installation, but sometimes this registration does not take place due to some environmental issue. The non-registered dll may cause different unexpected errors including but not limited to unexpected report layouts, inability to execute test cases from offline package and so on. In case you find such issues, ensure that the dll registry is proper by following the steps below:

How to validate QualitiaCore.dll is not registered?

Create a .vbs file, put below code snippet into it and save it to a location on your drive. Execute (double-click) this .vbs file. If any error message appears it indicates QualitiaCore.dll is not registered. If it does not show any message this means registry is alright.

Dim logs, conn
Set logs = CreateObject("QualitiaCore.QLogger")
Set conn = CreateObject("QualitiaCore.DatabaseConnectionHelper")
msgbox err.description

How to register QualitiaCore.dll?

If you find the error explained in step 1, then follow steps below.

Launch Command Prompt as an administrator.
Navigate to the folder where you have stored offline package.

Execute the following command:

"C:\Windows\Microsoft.NET\Framework\<Version_Number>\RegAsm.exe" /codebase QualitiaCore.dll

If the registration is successful then appropriate message will be displayed on the command prompt.

Could not find a part of the path 'C:\Xml\Suite.xml'

This issue occurs when somehow xml folder is not created during the installation process. You can create a folder named as xml at the C drive to resolve this issue.

Unable to Execute Test Cases in Internet Explorer

When a test case execution starts in Internet Explorer, the Internet Explorer does not open, and UFT closes. Also, in the Errorlog.txt, a message is displayed as “Testcase xml is missing”.

The reason is due to unavailability of the relevant add-in of the Internet Explorer for testing the application.

Solution:

Open the UFT, specify the application URL, and the browser as Internet Explorer.
Click the Record button.
A pop-up message opens which shows the message as “Some third-party add-ins are required to launch this URL. Do you want to enable these add-ins?”
Click Yes to enable the required add-ins.
Record few steps and save them.
Run them through UFT.
If the execution is successful, open the Internet Explorer, and check the name of new add-in enabled.
Run the test case through Qualitia.

Unable to Launch Qualitia Desktop Client

Problem: The Qualitia Client is not opening and also you do not see any error message.

Reason: Your organization’s security policies may be restricting the Qualitia Client from opening.

Workaround: Perform the following steps to resolve the issue.

Go to %Localappdata%\QualitiaQTPClient\app-x.x.x.
Note: x.x.x refers to the Qualitia for Desktop version you have installed.
Open the Qualitia.exe.Config file.
In the <runtime> node, between </assemblyBinding> and </runtime>, enter the following tag:
<enforceFIPSPolicy enabled="false" />
Save the configuration file.
Open the Qualitia Client.

Browser not supported