cancel
Showing results for 
Search instead for 
Did you mean: 

"Server not started" error on master after successfull tests

SOLVED
Highlighted
Contributor

"Server not started" error on master after successfull tests

Hi,

We have started to get problems with our tests on one of our setups. Or setups consists of two slaves (running TestExecute) connected to a master (running TestComplete), and the tests are running in sequence on the slaves.

 

One of these setups has now started to fail: One of the slaves runs all the tests, but the other stops after running only a few of the tests (two or three tests). The log on the master says "Server not started", and the log of the successful test on the slave does not contain any failures.

 

I can successfully verify the failing slave from the master project, and ping, remote desktop and windows file sharing works both ways.

 

Host OS: Windows 10 Enterprise 2019 LTSB Build 1809

TC: 14.40.1658.7 x64

TE: 14.40.1658.11 x64

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Community Manager

Re: "Server not started" error on master after successfull tests

Hi @stein_oddvar_ra,

I suppose this is a network issue. Try using the recommendations given in the Message - Verification failed help topic. Another possible solution is to use the IP address as a host name (instead of the network name).

 

As far as I understand, all the tests are run successfully despite this error, right? You can also submit a request to our Support Team via our Contact Support web form - perhaps they can suggest more troubleshooting steps. 

---------
Tanya Gorbunova
SmartBear Community Manager

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today

View solution in original post

4 REPLIES 4
Highlighted
Community Hero

Re: "Server not started" error on master after successfull tests

What's in the log from the failing machine?

Highlighted
Contributor

Re: "Server not started" error on master after successfull tests

There is nothing unusual in the logs on the failing slave. We can open the log of the last test that ran, and there is nothing there that indicates any problem. The next test is never started.

 

The only error we get is on the master - the "Server not started" error.

Highlighted
Community Manager

Re: "Server not started" error on master after successfull tests

Hi @stein_oddvar_ra,

I suppose this is a network issue. Try using the recommendations given in the Message - Verification failed help topic. Another possible solution is to use the IP address as a host name (instead of the network name).

 

As far as I understand, all the tests are run successfully despite this error, right? You can also submit a request to our Support Team via our Contact Support web form - perhaps they can suggest more troubleshooting steps. 

---------
Tanya Gorbunova
SmartBear Community Manager

Learn SmartBear products in a fun and easy way and prove your knowledge!
>>Participate in the TechCorner Challenge today

View solution in original post

Highlighted
Contributor

Re: "Server not started" error on master after successfull tests

Hi,

 

Thank you for the suggestion. The "Verification failed" is not relevant. When I try to verify the slave, the verification succeeds.

 

When I try to run tests, the slave runs one or two tests, then stop. On the master, the error "Server not started" can be found.

 

I will contact support.

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors