Hi,I have a local PC and a virtual machine. On the local, I am able to use the ID-based license without issue as administrator user. On VM, I am not an administrator. When I try there, nothing happens when I click "Open Login Page".When I set Testcomplete to run as administrator, this process works. Used Microsoft Edge.What would be some permissions related issues that could be causing this? Is there a log I can check to see what's being blocked on the backend? If we could get this working without needing admin privileges, that would be appreciated. Thanks

Restarting the VM solved the problem for whatever reason. Thanks for the resources.

ID based login only works as admin

Hassan_Ballan
Champion Level 3
8 months ago
On the VM login as the regular user you intend to use and login to your license to save for that user https://support.smartbear.com/administration/docs/en/smartbear-license-management/work-with-smartbear-license-management/license-management-for-license-users.html
pse
Occasional Contributor
8 months ago
Seeing this error from the access key.
- Hassan_Ballan
  Champion Level 3
  8 months ago
  On the VM as a user can you run TestComplete? For the first time it should ask you to login to your license.
  
  As an alternative, you can navigate to https://manage.smartbear.com to login. TestComplete should work normally now.
  
  The Access Key is only required for headless browser and not sure about your setup. Is that windows user a locked down user?
rraghvani
Champion Level 3
8 months ago
Is there any reasons to run TestComplete with Administrator privileges? Ideally, it should work fine without admin permissions, unless you are accessing resources on your local PC that requires admin permissions!

When TestComplete was installed, was it installed for All Users?

Does your VM, have access to the Internet or your license server?

Read through https://support.smartbear.com/testcomplete/docs/general-info/configuring/index.html and https://support.smartbear.com/testcomplete/docs/licensing/id-based/index.html
- pse
  Occasional Contributor
  8 months ago
  Restarting the VM solved the problem for whatever reason. Thanks for the resources.