StaffTo be certain, go back to the License Manager on your bare-metal physical machine and verify that your licenses are still present. If you expect to run TestExecute then (naturally) you should have an active TestExecute license.
(Note that the HASP-based TestExecute licenses were always floating, never node-locked).
Then reexamine the base image used to create your Jenkins images. There should be no licenses activated on it and it should be able to see your License Manager machine, and be able to access a TestExecute license from the License Manager.
(Note: If you activated a license in your base image those licenses will not be valid in any cloned images derived from the base image. )
If you can manually run TestExecute on your base image, try manually running TestExecute in a cloned Jenkins image on the machine where your tests are run. Perhaps the problem is that the local License Manager in your Jenkins image cannot find the network License Manager (the one serving the licenses). Maybe you need to configure the local License Manager on the base image (and cloned images) to explicitly specify where the network License Manager is.
The License Manager software is always installed. If you have a license activated on the machine, then the License Manager serves the license. If you don't have a license activated on the machine, then the local License Manager acts as a broker and checks the network for a machine that is serving licenses. Check the License Manager docs for more info on how to configure it:
https://support.smartbear.com/testcomplete/docs/licensing/key-based/how-to/license-manager/index.html
