QTP/UFT Support Tip: Error: “Following client components were not downloaded successfully”
We have seen multiple times and issue in which a user receives an error in QuickTest Professional (QTP)/Unified Functional Testing (UFT) when connecting to ALM/QC: “Following client components were not downloaded successfully”, and there is a list of DLL components after the message.
There will be tons of causes for this issue, but most common will be permissions on the client machine and some additional settings or configuration. As an initial troubleshooting, users and try the following steps:
- Use the "Run As Administrator" option to run QTP (right click on QTP icon -> Run As Admin)
- Disable the UAC feature by going to: Start > Control Panel > User Accounts > Click on "Change User Account Control settings" link > Slide the slider bar to the lowest value (towards Never Notify) > Click OK to save all changes, then reboot the machine.
- Sometimes this issue are caused due a Windows User with no Full Admin Rights, To work/execute QTP, users need to have Full Admin Rights, for more details check the following article: What are the minimum permissions required for QuickTest Professional (QTP), Service Test (ST), Sprinter (SP) and/or Unified Functional Testing (UFT)?.
- Check/Ask your System Administrator to logging into your machine (with his credentials) and try to reproduce the issue.
- From IE, disable the "Enable memory protection to help mitigate online attacks" option in the Internet Options -> Advance tab.
- Add the ALM/QC URL to the “Trusted Sites” from IE security settings.
- Delete the TD_80 cache folder contents. To erase it, go to Start > Run... > type %temp% and erase/remove the TD_80 folder, as it will be created once again after connecting to QC/ALM. And all QC/ALM components on the folder: C:\Program Files (x86)\Common Files\Mercury Interactive
- If multiple RDP sessions are attempting to connect to different versions of Quality Center (QC) from Quicktest Professional (QTP) simultaneously, the same error is reported. On this case, either make sure that all QTP sessions are accessing the same version of QC, or else for all QTP connections to QC, in every session on the machine, QTP must first be disconnected from QC before any QTP session can connect to a differing version of QC.
[If this post or any other post helps to resolve your issue or query, mark the thread as solved and give KUDOS to the author for their assistance. ]
(Posts and opinions made here are my own and do not reflect the opinions of my employer HP in any way)