Votes
Answers
Views
Question
2
1
254
We've been upgrading our Windows 10 build 1903 to Windows 10 build 1909 and now our UFT scripts won't run. Has anyone seen this? Is there a remedy? UFT will launch but the scripts won't execute.
2
1
220
Tags:
We've upgraded from 14.53 to 15.01. This code worked in 14.53 without any problem: DataTable("dtStart",GlobalSheet) = "2/5/2019 02:58:26" in 15.0.1 it does not work anymore and we have not been able to determine why.
2
1
87
Using UFT 15 and the Flight GUI sample application, UFT is seeing the application as a single WinObject. I cannot select the individual objects such as Username, Password, OK button or Cancel button. Is there a way to resolve this and be able to select each object?
2
1
574
I have Chrome set to restore specific tabs so on startup it loads the previous URLs that were open in the browser. I use SystemUtil.Run to launch Chrome, and when I do, I now have duplicate tabs on the browser, which confuses UFT and it won't interact with the correct objects. Is there a way to clos...
2
1
390
We are currently using UFT 12.54. We found out that Micro Focus stopped committed support for this version in July 2019. We need to upgrade to a stable version that still has some support life left. What version is recommended, and how much support life is left for the recommended version?
2
1
34
For some reason, I don't know why, our systems guys make our %appdata% folder reside on a network drive. With %appdata% configured like this, UFT 14.53 won't launch. Does anyone know how to make it work like this?
2
1
183
We have a few legacy QTP core licenses. Can I still use the latest UFT software? If so, any limitations?
2
1
57
We are using UFT Developer boxes configured to use RTE licenses. We need to be able to fallback to our pool of Full licenses once all RTE licenses are consumed, but this isn't working trying the different keys one at a time in our AutoPass License Server UFT.xml file. Any help?
2
1
77
We have a few UFT clients that can't connect to our AutoPass License Server. Others can. On the affected clients, we've double-checked TCP port 5814 is definitely open (verified by PortQuery showing LISTENING between client and server on that port). Any ideas?