Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am attempting to run tests on a remote agent by using a test controller that is on the same remote machine. I have set up my TestSettings file as follows:

<RemoteController name="MachineName" />
<Execution location="Remote">
    <AgentRule name="AllAgentsDefaultRole">

When I tell MSTest to execute a selected test in release or debug mode, it successfully builds the project and then returns "Failed to queue test run 'run name': No connection could be made because the target machine actively refused it." Visual Studio 2013 has been installed on the controller/agent machine, and the agent, controller, and client can all communicate successfully. Default ports are being used for communication (6901 and 6910), and telnet is able to connect. How do I get the test executing successfully?

share|improve this question
Have this exact same problem. Did you find the solution? – JL. Oct 23 '14 at 13:18
It looks like you cross posted this on SO…. Can you add the answer here as well? – Dan Snell Jan 22 '15 at 19:14
Thanks for the reminder, @Dan. – Ryan Cox Jan 23 '15 at 12:18

Found the answer. Agents cannot debug remotely, and while the build I was executing against in the above post was "release" (in one instance), I was still attempting to debug. If I select the test and click "Run" instead, it executes successfully on the remote agent.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.