This section describes troubleshooting and limitations for installing UFT.
Ensure that you have the Microsoft update https://support.microsoft.com/en-us/kb/2999226 installed before installing UFT.
If the installation fails, repair the Microsoft C++ 2015 Redistributable installation (found in the <UFT installation directory>/prerequisites folder) and try the UFT installation again.
Due to the Help documentation being online, the Help_Documents silent installation parameter is no longer supported. If you have silent installation scripts that use this parameter, remove it from your scripts to ensure UFT installs correctly.
If the UFT Files in Use dialog box is displayed during the installation process, select Close the application and attempt to restart them.
UFT automatically closes the applications and continues the installation.
If after restarting, the UFT Files in Use dialog box lists Explorer as the open application, do one of the following:
|Close the applications and attempt to restart them||
Instructs UFT to automatically close the applications that are needed for the installation.
|Do not close application.||
Instructs UFT to continue the installation. You must restart your computer after the installation if you select this option.
Component registration failed
If a message is displayed during installation about component registration failing, do not click OK to continue.
Instead, check the issue in the VC2015Prerequisite_yyyymmdd_XXXXXX.log file in the %TEMP% directory. If the log shows that a service did not start correctly, restart the service manually, and start your installation again.
UFT may work unexpectedly after uninstalling LoadRunner version 11.50. If this occurs, perform a repair installation for UFT after uninstalling LoadRunner 11.50.
Additionally, if you install LoadRunner 11.52 Patch 1 after installing UFT12.53, make sure to reboot the computer after installing LoadRunner. Otherwise, you may receive errors referring to the mdrv process.
|Sprinter||If you are using both UFT and Sprinter on the same computer, and you modify either UFT or Sprinter, you must run a Repair for the installation of the other product.|
When an ALM client is installed on the same computer as UFT, uninstalling UFT 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 LeanFT 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 LeanFT plugin available.
Workaround: After installing the required IDE, run a Repair for the installation.
|Microsoft Office 64-bit||
You cannot install Microsoft Office 64-bit on a machine with UFT. Instead:
|Windows 8.x or higher / Windows Server 2012 R2||
When using UFT on Windows 8.X or higher or 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 31 or later, Chrome automatically downloads and installs the Functional Testing Agent for Google Chrome the first time you open Chrome after UFT is installed.
In the following cases, you must manually enable the Functional Testing Agent for Google Chrome extension:
For details on manually enabling the extension, see the task on How to Enable the Functional Testing Agent for Google Chrome Extension in the Web section of the Unified Functional Testing Add-ins Guide.
Firefox versions 33 or later
If you are testing applications in Firefox version 33 or later, accept the prompt for install Functional Testing Agent for Firefox the first time you open Firefox after UFT is installed.
Firefox versions 32 or earlier
If you testing applications in Firefox version 32 and earlier, do the following:
If you are testing Java applets, you must use the legacy Functional Testing Agent for Firefox.
Legacy Functional Testing Agent for Firefox
The legacy Functional Testing Agent for Firefox is supported only for Firefox versions 39 and earlier.
Note: If you are using a version of the Functional Testing Agent for Google Chrome from UFT version 12.00 or earlier, you must enable the downloaded extension and remove the previous version of the Functional Testing Agent extension.
|Installing with administrator privileges||
UFT loses support for 64-bt appliations if a user with administrator priveleges installs the Unified Functional Testing Add-in for ALM, or performs a Repair operation on the Run Results Viewer, and the a user runs UFT on that same computer without adminsitrator priveleges.
Workaround: Log in as an administrator and do one of the following and Repair UFT or run <UFTinstallation>\bin64\Mediator64.exe.
|32-bit and 64-bit applications||
If your computer has two versions of an application, where one is 32-bit and the other is 64-bit, UFT 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.
|.NET / WPF Add-in extensibility||When working with .NET or WPF Add-in extensibility for a 64-bit Windows Forms process, the custom server DLLs must be built using the Any CPU option.|