White popup on the first TestExecute run
Hi, I have got a virtual machine that, before executing the automatic tests through an Azure DevOps release pipeline, is reverted to a checkpoint. The checkpoint contains an installed Test Execute ...
Forum Discussion
Hi Simona,
My wild guess about this white window is that this may be a kind of 'contacting license server' web page message that is displayed via Internet Explorer which is set as a default browser on this system and IE cannot render this web page.
How do you access TE license in pipeline?
We here use the the -accessKey parameter (https://support.smartbear.com/testcomplete/docs/licensing/id-based/automated-builds.html) and I do not remember ever having problems with license access (though we do not restore test box from snapshot).
Below is corresponding .yaml task configuration:
- task: InstallTestCompleteAdapter@1
displayName: TestComplete test adapter installer
condition: SucceededorFailed()
continueOnError: true
inputs:
installExecutor: true
updateExecutor: false
searchMode: ProjectItems
logsLevel: 0
accessKey: '$(SBAK_ALK)'
preferredExecutor: TE
Hi AlexKaras ,
I've got Microsoft Edge browser as default browser, so maybe the first hypothesis is not appening.
Within the yaml pipeline, I don't use the accessKey field, is it suggested to be used?
This is my yaml task:
Hi,
> Within the yaml pipeline, I don't use the accessKey field, is it suggested to be used?
I am not sure if it is suggested, but documentation (see the article I referenced in my first reply) mentions that it can be used and provided either via Adapter or via command-line (if Adapter cannot be used for some reason and you prefer/are forced to use command-line instead of Adapter-VSTask pair).
I don't expect any harm if you give it a try and make pipeline to use accessKey.
P.S.
> issue happens also without the Azure DevOps pipeline
As a quick check, you may try to restore from checkpoint and start TestExecute manually using command-line with accessKey parameter provided.
P.P.S.
Also check in TE's options if TE is set up to check for updates on start. This white window also might be a window that tries to tell you about existing update.
Ok thanks for the suggestion!
I'll try to apply this key to the yaml task and see if the issue newly appears.Hi Simona,
> Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)
BTW, just recollected that I had an error with this code for myself. I am not sure if there was this white window, but the root cause was a licensing issue. Here is a quote to Support:
To reproduce the problem, I just started TestExecute on some other box so that the only available license is consumed and started the pipeline task.Pipeline fails on Visual Studio Test step which, as per my understanding, internally consumes the functionality provided by TestComplete Test Adapter.Visual Studio Test step fails with the "Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))" message.Pipeline executes without any problem as soon as TestExecute on another box is closed and the license becomes available.
In addition:Actually, Silent.log file confirms my statement with this message:"Tried to open the error dialog. Message: All the product instances allowed by your license key are already in use (running).."
The strange thing in your case is that it occurs on the first run only, but nevertheless the overall problem looks to me like something related to license access...
Try to check silent.log for TE on VM to see if it contains some useful information.
