unable to connect to the remote instance of testcomplete (testexecute)

[Phanindra]

I am seeing the following message if I try to run the tasks synchronously. However, I am able to run individual tasks separately through job details page.

The firewall is turned off in both master and slave machines, and the verification is also successful. Please find the attached file for more details.

TestComplete Version: 14.50.976.7 x64

I have also tried to run the tasks through script but I got same error.

Script:

function Test()
{
var JobName = "CRUD_Operations";
var Job = NetworkSuite.Jobs.ItemByName(JobName)
var Tasks = Job.Tasks
var Num = Tasks.Count
for (var i = 0; i < Num; i++)
{
//Tasks.Items(i).Run(true)
Tasks.Items(i).Run(false)
}
}

I would like to give you some more information on the set up which I am using to simulate the distributed testing;

I have a node locked license (which is a server) (Version: 14.50.976.7 x64)

On two VM's I have installed a trial version of TestExecute. (Version: 14.50.976.11)

Appreciate your help on the same.

[sonya_m]

Thank you for posting your question here! Let's ask the Community.

@tristaanogre @Wamboo @cunderw @anupamchampati , could you check this thread and let us know if you could suggest something? Thank you🙂

[Wamboo]

Hi, sorry Sonya, but I'm not using the Network Suite project right now. I can't help you here.

[Phanindra]

May I know why this question of mine is not answered yet?

Fyi, there is also a support ticket which I have created (Ref: Case #00444800: Distributed testing issue) since I was not getting any suggestions/solutions from this community on this issue.

Kindly let me know if you need more information.

Thanks!

[sonya_m]

Hi @Phanindra ! I just replied to your private message. Please keep working with our Support Team, since it looks like this requires deeper investigation. Thank you.

[pandiyaraj]

Hi,

I am also facing same issue with Windows server 2016 setup. Any solutions?

[Phanindra]

I got to know the problem in my system. If you have a license combination like this;
TestComplete - Node-locked
TestExecute - floating, 1 seat
TestExecute - floating, 1 seat, 30 day trial period
TestExecute - floating, 1 seat, 30 day trial period

Assume the trial period ends for the test execute, then if you try to run the tests via distributed testing which kicks in all 3 VMs simultaneously then we will land up with this situation. 

The solution in this case would be release the test execute license after the test execution or else make the Test Complete (for test execute) service manual (under services.msc) and then kill/stop the process after test completion.

Unfortunately the error message which is displayed during the execution is not proper and its confusing too. That error message is too abstract and debugging is very difficult.

Hope this helps.

Thanks!

Phani