Instructs OpenText Functional Testing to automatically close the applications that are needed for the installation.

Instructs OpenText Functional Testing to continue the installation. You must restart your computer after the installation if you select this option.

When an ALM client is installed on the same computer as OpenText Functional Testing, uninstalling OpenText Functional Testing may remove the association of movie (.fbr) files.

This may prevent you from viewing movies associated with defects in ALM using the Micro Player application.

Workaround: Re-associate the movie files with the Micro Player application from the Windows File Options dialog box.

• In the Custom Setup screen, it is possible to select the OpenText Functional Testing for Developers Visual Studio or Eclipse plugins even if you do not have the relevant IDE installed at the time of the installation.

  If you install the IDE later, you will not have the OpenText Functional Testing for Developers plugin available.

  Workaround: After installing the required IDE, run a Repair for the installation.

• Make sure to use the new syntax when silently installing OpenText Functional Testing for Developers as part of the OpenText Functional Testing installation.

  For details, see ADDLOCAL values for OpenText Functional Testing for Developers components.

  If you encounter an error similar to this one, make sure you did not use the old LeanFT silent installation command syntax:

  Error: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2711. The arguments are: LeanFT

• When installing OpenText Functional Testing on a Windows 10 or 11 operating system, you must close Cortana and the Action Center before performing the OpenText Functional Testing installation.

• You must have administrative permissions to connect to ALM from OpenText Functional Testing on Windows 10 or 11.

  Connect to ALM with Administrator permissions immediately after installing OpenText Functional Testing.

To debug GUI tests in OpenText Functional Testing, ensure that you have the pdm.dll file installed and registered.

The pdm.dll file is installed and registered with Microsoft Visual Studio and Microsoft Office, and installed (but not registered) with Microsoft Internet Explorer.

Alternatively, install the Microsoft Script Debugger provided with the OpenText Functional Testing installation, which provides the pdm.dll.

To register the pdm.dll file installed with Microsoft Internet Explorer:

1. Ensure that you have administrator privileges.
2. Locate the pdm.dll file, usually located either in c:\program files(x86)\internet explorer\ or c:\program files\internet explorer.

3. Move the pdm.dll file and the msdbg2.dll file from the same folder to a different location.

4. Run the following commands:

   regsvr32 <full path to pdm.dll>\pdm.dll

   regsvr32 <full path to pdm.dll>\msdbg2.dll

If your currently registered pdm.dll version is lower than 9:

1. Uninstall the Microsoft Script Debugger (if installed).

2. Install the Microsoft Script Debugger using the OpenText Functional Testing Additional Installation Requirements utility.

   Open the OpenText Functional Testing Additional Installation Requirements utility from the Windows Start menu or by running <Installdir>\bin\UFTInstallReqs.exe.

Using OpenText Functional Testing and Microsoft Office 64-bit on the same machine requires some intervention. This is due to a conflict between the Microsoft Access Database Engine versions used by these two programs.

Do one of the following: 

• Install OpenText Functional Testing before you install Microsoft Office 64-bit.

• Before you install OpenText Functional Testing, install Microsoft Access Database Engine 2016 32-bit from an administrator command line, using the /quiet argument. For details, see Install Microsoft Access Database Engine 2016.

• Install OpenText Functional Testing with the SKIP_MSADE_CHECK flag. This installs OpenText Functional Testing without requiring the Microsoft Access Database Engine 2016 Redistributable to be installed.

  Silently: 

  cmd /c MsiExec /norestart /qn /i "<OpenText Functional Testing MSI Path>\Unified_Functional_Testing_x64.msi" /l*xv "<log file path>.log" SKIP_MSADE_CHECK=1

  Using the installation wizard:

  cmd /c MsiExec /norestart /qf /i "<OpenText Functional Testing MSI Path>\Unified_Functional_Testing_x64.msi" /l*xv "<log file path>.log" SKIP_MSADE_CHECK=1

  You can install the redistributable engine as described above, if you find later that you need it for API database activities.

When using OpenText Functional Testing on Windows Server 2012 R2, if you want to use API tests and components, make sure that you have MSU (Microsoft Update) KB2887595 installed.

If you are testing applications in Google Chrome version 68 or later, Chrome automatically downloads and installs the OpenText UFT Agent for Google Chrome the first time you open Chrome after OpenText Functional Testing is installed.

In the following cases, you must manually install the OpenText UFT Agent Chrome extension:

• You have no Internet connection.

• You have not enabled the automatic updates for Google Chrome.

• You are using Google Chrome version 67 or earlier.

• You are using Google Chrome version 95 or earlier.

For details on manually installing the extension, see Enable the OpenText UFT Agent extension on Google Chrome.

The first time you open Firefox after OpenText Functional Testing is installed, accept the prompt to install the OpenText UFT Agent for Firefox.

To use the latest OpenText UFT Agent browser extension, make sure its older version, the Functional Testing Agent extension is not installed. If both extensions are installed, manually remove the older before enabling the new.

OpenText Functional Testing loses support for 64-bit applications if a user with administrator privileges installs the UFT One Add-in for ALM, or performs a Repair operation on the Run Results Viewer, and then a user runs OpenText Functional Testing on that same computer without administrator privileges.

Workaround: Log in as an administrator and do one of the following:

• Repair OpenText Functional Testing

• Run <Installdir>\bin64\Mediator64.exe.

If your computer has two versions of an application, where one is 32-bit and the other is 64-bit, OpenText Functional Testing always opens the 32-bit version.

This occurs when the operating system performs a redirect from the Program Files folder to the Program Files (x86) folder, and from the System32 folder to the SysWow64 folder.

Workaround: To specify a 64-bit version, make sure that the step explicitly states the path to the 64-bit application.