Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    7
  • Subscribers subscribers
    13
  • Views views
    1955
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error: The specified device could not be locked for use. Try another device

Carlos A Acosta
 

Hi Experts,

 

I have UFT Mobile 3.4 installed with UFT one 15.0

UFT Mobile is integrated with AWS Device Farm with self-signed certificates.

When I try to open a cell phone from ADF it asks me to accept the certificates, I accept the risk, but the following error message appears:

The device could not be locked. This will limit your interactions with the device. Contact your administrator to check the status of your license.

error UFTM.png

When I try to load the device from UFT One, I get the following error message:

The specified device could not be locked for use. Try another device.

error UFTM.png

 

I try with different devices but the error was the same.

I appreciate any help.

 

Thanks,

 

Carlos Acosta

Tags:

  • 0  

    Hi Carlos,
    I’d suggest to go to Administration > Licenses > Quota allocation and make sure that you have available licenses.

    Regards,
    Alvaro

  • 0   in reply to   

    Thanks for your quick answer Alvaro.

    I checked the license, but it is ok as you can see in the next screenshot. I have 5 concurrent devices availables.

     

    error UFTM.png

  • 0   in reply to   

    Hi Carlos,
    The screenshot you shared is showing the total capacity of your license. Now, you can distribute those licenses across different workspaces through the Quota allocation option:
    QuotaAllocation.jpg

    For extra details, feel free the check the link below:
    https://admhelp.microfocus.com/uftmobile/en/3.4/Content/Admin-Licenses.htm

    Cheers!
    Alvaro

  • 0 in reply to   

    Hi Carlos,

    I would also like you to pay attention to UFTM online documentation, that provided the need to use fixed IP address only when using self signed certificates:

    https://admhelp.microfocus.com/uftmobile/en/3.4/Content/AWS installation.ht

    1. The connection to the ADF server is a secure SSL connection. If you intend using the ADF server's self-signed certificate, copy the IPv4 Public IP from the Description tab of the instance to your clipboard. When using a Certificate Authority (CA) certificate, use the DNS address used to create the CA certifiate.

    Tip: By associating a fixed IP address with an EC2 machine, you can avoid having to change the IP details after reboot. A reboot is only necessary after assigning a fixed AWS Elastic IP to an ADF Server. The reboot is required to regenerate the self-signed certificate on the ADF server installer due the change in the IP address. For details, see the AWS documentation.

     

    In case you still have any questions or doubts, please emails us on mcfrd@microfocus.com and the UFTM CFRD team will help you further.

    Regards,

    Erez.

  • 0   in reply to 

    Thank you!

    now, I can see the device, but from UFT One appear the next error message: "Failed to open the Mobile device viewer window".  My question is, it is about certificates?

     

    When I try to open the device from UFTM I need to accept the risk about the certificate:

    error UFTM.png

     

    Then ADF Server load ok

    error UFTM.png

    Then the device load ok

    error UFTM.png

     

    But when I try to run o record from UFT One, the next error appear:

    error UFTM.png

    This error is associate to certificates?

    Thanks!

     

    Carlos Acosta

  • 0 in reply to   

    Hi Carlos,

    although you are using Self signed certificate, you should still be able open the device viewer and accept the certificate. it seems that a different error occurred here , that prevented UFT One tool to open the device viewer, it might be UFT configuration or maybe permission issue. I would suggest to investigate the UFT one logs to find the root cause.

    Regards,

    Erez.

  • 0   in reply to 

    Good Morning,

    I want to tell you that we updated UFT One from version 15.0 to version 15.0.1 and it worked perfectly.

    I want to thank all the support provided!

    Thank you very much!

    Carlos Acosta

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.