Forum Discussion

Phanindra's avatar
Phanindra
Occasional Contributor
5 years ago

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

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 maste...
Phanindra's avatar
Phanindra
Occasional Contributor

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's avatar
sonya_m
SmartBear Alumni (Retired)
5 years ago

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's avatar
    pandiyaraj
    New Contributor
    4 years ago

    Hi,

     

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

    • Phanindra's avatar
      Phanindra
      Occasional Contributor
      4 years ago

      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