locked
Failed to register this test agent with the test controller RRS feed

  • Question

  • The problem is I can't configure test agent and continue receive that "Failed to register this test agent with the test controller". There is no firewall or antivirus in my machine. and iam using VS2012 the user also has administrative rights as well.

    ************************************************************************************************
    Configuration started on 2013/04/30, 06:07:04.
    OS Version : Microsoft Windows NT 6.1.7601 Service Pack 1
    Executable version : 11.0.60315.1
    Server stack trace: 
       at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessResponseException(WebException webException, HttpWebResponse& response)
       at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
       at System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.get_ControllerVersion()
       at Microsoft.VisualStudio.TestTools.Execution.ExecutionUtilities.GetControllerVersion(IControllerAccessManager accessManager, Boolean tolerateOldControllers)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
       --- End of inner exception stack trace ---
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.GetControllerInformation(String controllerUri, NetworkCredential labServiceAccout)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.BindToController(String testController, ServiceAccount agentServiceAccount, NetworkCredential labServiceAccount)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.HandleControllerChange(AgentConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.Configure(AgentConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at Microsoft.VisualStudio.TestTools.AgentConfigUI.AgentConfigUI.ConfigureWorker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    I, 2013/05/02, 02:28:05.313, Work completed for GetConfiguration() call : got out of turn error
    E, 2013/05/02, 02:28:05.314, Failed to register this test agent with the test controller. Possible reasons could be you do not have permissions to connect to the test controller or a firewall is blocking the connection.
    To fix this problem, verify the test controller is running and you have appropriate permissions to register test agent with the test controller. 

    ram

    Thursday, May 2, 2013 10:06 AM

Answers

All replies

  • Hi ram,

    To fix this problem, verify the test controller is running and you have appropriate permissions to register test agent with the test controller. 

    As you said that if no firewall in your machine, I’m afraid that you would check the permissions in your machines.

    I suggest you refer this MSDN document “Setting Up Test Controllers and Test Agents to Manage Tests with Visual Studio”.

    If you run your test controllers and test agents on machines that are in a work group and not in a domain, or machines that run in different domains that do not have a two-way trust relationship, you must follow these steps as part of your installation process:

    1.On each computer where you will install a test controller or a test agent, create a local user account that is a member of the Administrators group. Use the same account and password on each machine.

    2.Use this user account for your test controllers when you install and configure them.

    3.Add this account to the TeamTestAgentService group on the test controller machine.

    4.Install and configure your test agents using this same account.

    It also shared the user accounts that you must add to each group. Hope it could help.

    Reference:

    http://social.msdn.microsoft.com/Forums/en-US/vstswebtest/thread/1f427ec0-8ef3-45d5-b013-57da18903937

    In addition, a Troubleshooting Guide for Visual Studio Test Controller and Agent, it shared us the useful information for the Visual Studio Test Controller and Agent issue.

    http://social.msdn.microsoft.com/Forums/en-US/vststest/thread/df043823-ffcf-46a4-9e47-1c4b8854ca13

    Have a nice weekend,


    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, May 3, 2013 9:12 AM
  • For those who still are looking for an answer, here is my solution. All these steps were executed on the test controller / test manager machine (which is the same machine in my case) :

    1 - I'm not sure if this is related to my problem but this was something I did before the following steps. At some point I've tried to install the VS Agents separately to the test agent machine. It didn't help to solve my problem but I could see to which machine it was being registered. After executing one of the following steps (I can't remember which one) I saw it being registered to a machine name which was on the test controller's hosts file pointing to 127.0.0.1. I've deleted those records from the hosts file. Now the localhost is pointing to 127.0.0.1 and after completing these steps the test agent is being registered to the test controller with the right machine name.

    2 - Since I have two network adapters on the test controller/manager machine, I've added the "bind to" key to the QTControllerConfig.xml file according to this article http://support.microsoft.com/kb/944496/en-us 

    I didn't add it to the QTAgentService.exe.config on the Test Agent and to the QTAgent.exe.config on Test Controller.

    (I don't believe that this step was necessary but it's worth mentioning)

    3 - On the test controller, I've deleted the cache in this directory : C:\Users\username\AppData\Local\Microsoft\Team Foundation\4.0\Cache

    This step does not solve the issue by itself.

    4 - I've deleted the record about a former environment from the file QTControllerConfig.xml which is located at C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE.

    After these steps I could finally install the test agent to my virtual machine from the test manager.


    • Edited by enmosarge Friday, October 11, 2013 8:34 AM missing step
    Friday, October 11, 2013 7:21 AM