QTP How to Fix ALM/QC connection issues after upgrade
QTP ALM/QC connection issue after upgrade
The good news: my company finally upgraded last month from QC 10 to ALM 11. The not-so-great news is that since the upgrade, I’ve been dealing with lots of questions and issues from QTP users trying to connect to ALM11.
The two main issues are QTP hanging when trying to connect to ALM, or users continually getting “Access is denied” errors.
Here are the steps I’ve been using to resolve these issues:
Make sure that ‘Reconnect to server on startup’ is not selected
If a user has the “Reconnect to server on startup” selected, QTP will attempt to reconnect to the old ALM/QC server every time it’s started.
First, you should to make sure QTP doesn’t try to reconnect to the older ALM/QC instance, since it will attempt to automatically update the QC add-in control, inevitably causing version conflicts.
To do this, go into the mic.ini and make sure all the automatic logins values are set to 0.
-
Navigate to the directory in which QuickTest Professionalbin is installed.
- Make sure the ‘ReconnectToDB’ is not selected.
Uninstall the HP QuickTest Add-in for ALM-QC
- Under Windows’s Control Panel section, uninstall the HP QuickTest Add-in for ALM-QC.
Install the new ALM/QC HP Quality Center Connectivity
- Navigate to ALM/QC server Add-Ins Page (http://YourQCServer/qcbin).
- Click on the Add-Ins Page link.
- Click on the HP Quality Center Connectivity.
- Download the Add-in to your local drive. (If you’re running on Windows7, be sure to right-click on the TDConnect.exe and “Run as administrator.”
Start QTP and try connecting to the new ALM server
- Make certain the user is using the correct Server URL. The URL should not contain start_a.htm. The correct format is: http://YourQCServer/qcbin
-
If you get an error message saying WebClient.dll access is denied, and QTP is on a Windows7 machine, close QTP and right-click on the QuickTest shortcut then “Run as administrator.”
Going ALM Nuclear
If the above does not resolve your issue, try the following:
- Delete the TD_80 folder (if it exists) under your Windows Temp folder.
- Uninstall the QC add-in.
- Delete the “QuickTest Add-in for…” under the Program FilesHP folder.
- Delete the registry key HKEY_CURRENT_USERSoftwareMercury InteractiveQuickTest Add-in for Quality Center’
- Reboot’
- Re-install the QC add-in’
- Try again to re-connect in QTP.
Joe Colantonio is the founder of TestGuild, an industry-leading platform for automation testing and software testing tools. With over 25 years of hands-on experience, he has worked with top enterprise companies, helped develop early test automation tools and frameworks, and runs the largest online automation testing conference, Automation Guild.
Joe is also the author of Automation Awesomeness: 260 Actionable Affirmations To Improve Your QA & Automation Testing Skills and the host of the TestGuild podcast, which he has released weekly since 2014, making it the longest-running podcast dedicated to automation testing. Over the years, he has interviewed top thought leaders in DevOps, AI-driven test automation, and software quality, shaping the conversation in the industry.
With a reach of over 400,000 across his YouTube channel, LinkedIn, email list, and other social channels, Joe’s insights impact thousands of testers and engineers worldwide.
He has worked with some of the top companies in software testing and automation, including Tricentis, Keysight, Applitools, and BrowserStack, as sponsors and partners, helping them connect with the right audience in the automation testing space.
Follow him on LinkedIn or check out more at TestGuild.com.
Related Posts
Look, I’ve been doing test automation for over 25 years. I’ve heard the predictions. “Manual testing is dead.” “AI will […]
The 72.8% Paradox That Changes Everything After interviewing 50+ testing experts in 2025 and analyzing data from our 40,000+ member […]
Look, I’ve been doing this testing thing for over 25 years now. I first wrote about the AI “three waves” […]
What’s New in Low-Code/No-Code Testing for 2026 A lot had changed on the The low-code/no-code testing space and it has […]