Thanks for the additional notes for the environmental specifics on your end.
First thing I want to point to is that the Test Studio Scheduling setup requires a single Scheduler and Storage services host. It acts as a centralized controller for the execution machines - these, on the other hand, can be multiple machines and the minimum requirement is to have the Run-time installed.
Then, next thing to have in mind, is that the Test Studio standalone default installation does not include the services, where the Run-time default installation adds these automatically. Probably this is the reason you have these installed on both machines. However, this is not supposed to cause any troubles, if you use the services on one of the machines.
So, having said the above, here is how you can proceed:
1. Choose which of the machines will be used as a Scheduler and Storage services host. You mentioned that the remote machine's (VDE-EPIPC04) Scheduler seems to be configured and working, when you connect the Execution clients to it and I you can use it.
2. If this is the decision, please, open the Scheduling configuration wizard
on that remote machine, and click on Apply
for each of the tabs. You can start it by typing 'Configure as Scheduling Server
' in the Windows start menu.
3. Please collect screenshots of each tab, after clicking the Apply
4. Expected is that all services are started successfully.
5. Open the Execution clients on both machines - VDE-EPIPC04 and VDE-EPIPC10, and connect these to the configured Scheduler
6. In the Test Studio standalone on machine VDE-EPIPC10, connect the project
to that same Scheduler on VDE-EPIPC04
7. The Execution status view
main window should now display the two machines as Execution servers, and information for the configured Scheduler and Storage. Please, prepare a screenshot of the main screen in this view.
These steps are only to confirm if the setup is correctly configured, as I suspect you managed to get this working when reading the log files. So, in case you have performed the above, you don't need to reconfigure the setup again.
Next thing I would like to ask for is a simple test to verify if there are any further obstacles for the setup:
1. Add a new empty web test in the project and record a small sample test - simple navigate step and a click, or anything else.
2. Add this one to a test list and run this one remotely on the other machine.
If that test list is running successfully, we can be sure the Scheduling communication between the machines is not interrupted or restricted and can proceed further.
The log file you managed to generate and send me points that there is a successful attempt to run a test on the remote machine, but there are compilation errors for missing elements. These details will be also listed in the failed results displayed in the Calendar - to see the complete log for selected result, use the Execution Log
button (please, see the screenshot attached). Please, find additional details on these errors and how to solve them in this article
Once these missing elements errors are resolved, you should be able to run the tests on the remote machine.
I hope these notes will be helpful for you. Though, in case of further questions, please, get back to me.