| || |
QTP 11.5 Issues
Has anyone installed and successfully used QTP 11.5 (UFT 11.5)? I installed it yesterday and it locked up windows explorer every time I tried to record with it. I decided it was not ready for our use and uninstalled it. When I attempted to reinstall 11.0, I got an error during the installation stating that WWWPackage.dll could not be registered. No matter what I try, I cannot get this DLL installed and registered. QTP will not run without it.
I have uninstalled QTP, QTP Result Viewer, and HP Update. I deleted the full contents of the %TEMP% directory (including TD_80). I deleted all HP folders from program files (x86) and from \users\<me>\AppData. I deleted all references to UFT from the registry. I deleted many references to QuickTest from the registry but not all. The ones I left were file associations and other things that I felt would not impact installation.
Any thoughts? Is there an updated clean installer for 11.5? I tried version 2.10 with no luck.
Last edited by belewda; 01-03-2013 at 09:08 AM.
I have also found 11.5 to be unusable in its current state, something as simple as setting a break and clicking the local variables tab causes it to lock up and require killing via task manager! I like the new look and feel of it though and the new insight recording mode seems interesting but I was also having problems getting this to work without lock ups. I have it installed on a test VM so don't have the issues with rolling back but certainly won't be moving away from 11 anytime soon.
Last edited by SteveRS; 01-04-2013 at 02:32 AM.
I worked with 11.5 for about three hours yesterday. I like the new UI. Unfortunately, it locked up twice during runs at two different places for no apparent reason. I ended up using Task Manager to kill the program both times. This is not good. If SteveRS and I were able to see this problem so quickly, I would think the manufacturer would also have seen and fixed it. No, I am not ready to give up and go back to 11.0. Yes, I think the manufacturer should follow up on this and issue a patch ASAP. FYI, I am using it with Windows 7 Professional, SP1, English, 32-bit.
WinRunner was quite awful like this 18 years ago. Then it got quite good. Then QTP started out a bit clumsy at the start. It worked on only a few types of GUIs. Later it became very useful.
The annoying part to me and my clients is that a clean uninstall is nearly impossible. I learned from working with Mercury and now HP that it is best to use a machine that can be quickly re-imaged when trying out new builds of their software. It is quite sad that they cannot provide an uninstall utility that shows us the parts that need to be removed on the machine.
Try the update 11.5 uninstaller on below link and let me know if it helps
Originally Posted by tarunlalwani
Thanks for the updated version. Unfortunately, it did not resolve the problem.
I had my co-worker, who was having the same issues, try it out. He says he got the same error message after uninstalling, running the uninstaller, and then re-installing. I have a meeting today with our third-party vendor who sold us QTP. I'm hoping they have some tricks up their sleeves. if not, I'll likely be back soon.
Try this post. Not sure if you have Sprinter on your machine.
I tried again yesterday to get QTP 11 re-installed. After uninstalling, I spent hours cleaning up the registry, manually deleting everything that had UFT, QuickTest, or QTP in the key. I had no HP products installed. I looked for any signs that Sprinter was installed and nothing was there. I deleted all folders related to HP products. After all of the cleanup and a reboot, I tried re-installing. This time, WWWPackage installed and registered correctly but the BHOManager dll would not register.
I think I'm going to just have to wipe the machine and start over.
Can you manually register the DLL and post the error message that you are getting?
I tried with both 32 and 64-bit versions of regsvr32. In both cases, I got this response:
I even downloaded a new installation disc image from HP site, thinking maybe mine was corrupt. Same results.
The module "C:\windows\SysWoW64\BHOManager.dll" failed to load.
Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
The specified procedure could not be found.