TestComplete cannot create sessions from Jenkins

Hello Michael_B,

We here in the community don't know about time lines for fixes or if this is something that has been reported as a bug.  Have you checked with Support?  The easiest way to open a support ticket is through TestComplete directly from Help| Contact Support Team...

However, basic questions,

• Which version of TestComplete are you running.
• What changed? — Did anything update around the time both issues started: Jenkins, the TC plugin, TestExecute, or Windows?
• How is the Jenkins agent connected on the Windows 11 VM? — Windows service, JNLP, or something else?
• Is there an active, unlocked interactive session on the Windows 11 VM when the job runs? — Not just logged in, but unlocked and at the desktop.

My instinct is this is an upgrade or configuration change rather than a bug — either something updated in Jenkins, the TC plugin, or TestExecute, or Windows 11 tightened a remote session policy either through an OS update or a direct configuration change.

... If you find my posts helpful drop me a Like👍 Be sure to mark the post as the Solution✅ when you get one to help others out and to credit the one who helped you. 😎

Thanks for the reply Scott! It appears to be a Windows 11 cumulative update that broke it. Any cumulative update from February to their most recent breaks it. I have a ticket open with SmartBear support. They informed be that it has been marked as a blocker and the developers are working on it.

The test VMs are not logged on at all and we have the Jenkins agent configured as a service. We send different credentials to the VMs via the TestComplete Jenkins plug-in, they log in with the credentials provided by the job, and run the test cases via TestExecute. If we log onto the VM manually before running the jenkins job, it will work.

 This has been a key feature of the product that we rely on and tested before we purchased the product in 2022. Does it seem strange that we are running like this? Support said they have heard about it from other customers too, but I'm not seeing as much chatter in the community as I expected.

There have been previous instances where we needed to upgrade TestComplete to stay compatible with a new Windows or Edge patch in the past. I'm hoping this will be similar and they'll release a patch soon. Or, barring that, send out an announcement that they are removing this feature.

Michael_B​ 
We have the very same issue and have come to the same conclusion.

For the past 2-3 months we have been struggling with our CI breaking, due to TestExecute being unable to create user sessions (error code -10).

Jenkins -> TestComplete Plugin -> TestCompleteService -> TestExecute

We have also narrowed it down to the Windows Security patches breaking this functionality.

Whenever we uninstall those patches, it works again. We have paused the updates for the time being, but this is not a feasible solution.

Patching the Jenkins plugin and TestExecute to the latest version has not resolved this issue yet. We also haven't found any other solution or the specific reason yet, so we were unable to do anything except uninstall the most recent patches.

I have also already contacted support and will update here whenever I get a solution.

... so do I get the Solution on this one?  😁LOL  ...  I have very happy you found a fix (for now).  Have an AWESOME day!

"My instinct is this is an upgrade or configuration change rather than a bug — either something updated in Jenkins, the TC plugin, or TestExecute, or Windows 11 tightened a remote session policy either through an OS update or a direct configuration change."