locked
Unable to register test agent with test controller. RRS feed

  • Question

  • Please suggest me the forum if I posted it in wrong forum.

     

    I have a developer machine, wanted to setup test controller and test agent on the same box. I have installed and configured test controller and installed test agent successfully. When am trying to register test agent, am getting following error. Test controller is running with a local account which is an administrator and member of controller admin group. test agent account is a local admin and member of test agent service group. I have tried to start test controller with a domain account who is also a local admin, member of test controller admin group. Nothing worked out yet. Seems like test controller is working fine. I have enabled traces, not found any log files.  Thank you very much for the help.

     

    “Failed to register this test agent with the test controller. Possible reasons could be you do not have the right permissions to connect to the test controller testcontroller, or a firewall is blocking the connection.

    To fix this problem, verify that you are a local administrator on the test controller machine, and that the Windows Firewall Settings on the test controller machine has "File and Printer Sharing" exception.

    I, 2011/10/30, 10:16:42.684, Configuring ACL...”

     

    Following is the information in log file.

     

    Creating Channel

    I, 2011/10/30, 10:16:33.346, CreateControllerObject: attempt 0, System.Net.Sockets.SocketException (0x80004005): No such host is known

     

    Server stack trace:

       at System.Net.Dns.GetAddrInfo(String name)

       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)

       at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)

       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

       at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.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.GetControllerObject()

       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri)

    I, 2011/10/30, 10:16:37.949, CreateControllerObject: attempt 1, System.Net.Sockets.SocketException (0x80004005): No such host is known

     

    Server stack trace:

       at System.Net.Dns.GetAddrInfo(String name)

       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)

       at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)

       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

       at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.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.GetControllerObject()

       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri)

    I, 2011/10/30, 10:16:42.553, CreateControllerObject: attempt 2, System.Net.Sockets.SocketException (0x80004005): No such host is known

     

    Server stack trace:

       at System.Net.Dns.GetAddrInfo(String name)

       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)

       at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)

       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

       at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.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.GetControllerObject()

       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri)

    E, 2011/10/30, 10:16:42.655, Microsoft.VisualStudio.TestTools.ConfigCore.ConfigToolException: Unable to connect to test controller service testcontroller

       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri)

       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.AddAgent(String agentName, String controllerUri, ServiceAccount agentServiceAccount)

       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.BindToController(String testController, ServiceAccount agentServiceAccount)

       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.HandleControllerChange(AgentConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)

    I, 2011/10/30, 10:16:42.658, DetermineDomain:: User: NT AUTHORITY\NETWORK SERVICE

    I, 2011/10/30, 10:16:42.658, Domain: NT AUTHORITY

    I, 2011/10/30, 10:16:42.658, Machine Name: FRWU-T61P

    I, 2011/10/30, 10:16:42.679, Final Domain: NT AUTHORITY.  Final username: NT AUTHORITY/NETWORK SERVICE

     

    Sunday, October 30, 2011 8:29 PM

Answers

  • Hi,

    Your installing the test controller and the test agent on your dev machine. 

    Note - To install a test controller, you must be a member of the Administrators security group on the computer.

    1. The test controller is installed and configured to be run using a local administrator account, what permission does this account have with TFS? 

    Note - Test Controller In Same Domain: If you want to register your test controller with your Team Foundation Server project collection, the account that you use for the test controller service must be a member of the [Project Collection]\Project Collection Test Service Accounts group, or the account that you use to run the test controller configuration tool must be a member of the Project Collection Administrators group.

    Test Controller in Different Domain or Workgroup: If you want to register a test controller that is in a workgroup or a different domain that does not have a two-way trust with the domain for your Team Foundation Server, you must also create a local user account with the same user name and password on the Team Foundation Server machine and the test controller machine. This local user account must also be added as a member of the following Team Foundation Server group: [Project Collection]\Project Collection Test Service Accounts. Then you can register the test controller using this local user account when you run the test controller configuration tool.

    I believe you are under case 1, if so make sure that the user you are setting up to run the test controller is either a member of the [Project Collection]\Project Collection Test Service Accounts group or the Project Collection Administrators group. 

    Make sure you have registered your Test Controller with a Team Project Collection before moving on to install the Test Agent. 

    To install a test agent, you must be a member of the Administrators security group on the computer.

    2. Now coming down to installing Test Agent. 

    - If you want to use the IntelliTrace collector or the network emulation, the user account must be a member of the Administrators group.

    - If the agent user name is not a member of the TeamTestAgentService group it will be added to this group, which requires permissions on the test controller machine.

    The user for the interactive process must be a member of the TeamTestAgentService security group or the process will not be able to run the tests assigned by the controller.

    Try click on configure and see if it works?

    Since the test controller has been registered with the team project the test agents should be registered with the test controller without any issues. Make sure that in the text box where you have to specify the test controller name, you key in the correct test controller name and port number, for example MachineName:6901 if you chose the defaults while installing the test controller.

    Since you are installing both the agent and the controller on the same machine i don't see any issues that may be caused by the firewall. Yet you can try disabling the firewall temporarily on the machine if the configuration fails. 

    See this msdn article for more details => http://msdn.microsoft.com/en-us/library/dd648127.aspx#Security

    HTH
    Cheers, Tarun 

     


    Please remember to mark the replies as answers if they help.

    Tarun Arora

     

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader


    Sunday, October 30, 2011 10:09 PM
  • Hi ramesv,

     

    1.       About this issue” Is it mandatory to register test controller with Team Project Collection?”

     

    To determine whether register TFS or not, it depends on whether you’ want to use TFS resource, like MTM or Lab Management

     

    2.       Based on your description, when you register the test agent with the test controller, it generated this issue. So I think you could check.

     

    (1)    Make sure you are a local administrator on the test controller machine, and that the Windows Firewall closed.

    (2)    Under the controller name you should write the <machineName>:port and not serviceName:port.

    (3)    A reboot is still required for the actual configuration to be successful. See

    http://social.msdn.microsoft.com/Forums/en-AU/windowsazureconnectivity/thread/4502f378-cf47-4e67-bc15-5a5795d23d4d

     

    Similar threads:

    http://social.msdn.microsoft.com/Forums/en/vststest/thread/105b565f-2423-4559-b2e4-61cb8950808f

    http://social.msdn.microsoft.com/Forums/fi-FI/vststest/thread/492b3585-2795-49ee-96fb-9af22de5ccb4

     

    Thanks,


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, November 2, 2011 3:43 AM
    Moderator

All replies

  • Hi,

    Your installing the test controller and the test agent on your dev machine. 

    Note - To install a test controller, you must be a member of the Administrators security group on the computer.

    1. The test controller is installed and configured to be run using a local administrator account, what permission does this account have with TFS? 

    Note - Test Controller In Same Domain: If you want to register your test controller with your Team Foundation Server project collection, the account that you use for the test controller service must be a member of the [Project Collection]\Project Collection Test Service Accounts group, or the account that you use to run the test controller configuration tool must be a member of the Project Collection Administrators group.

    Test Controller in Different Domain or Workgroup: If you want to register a test controller that is in a workgroup or a different domain that does not have a two-way trust with the domain for your Team Foundation Server, you must also create a local user account with the same user name and password on the Team Foundation Server machine and the test controller machine. This local user account must also be added as a member of the following Team Foundation Server group: [Project Collection]\Project Collection Test Service Accounts. Then you can register the test controller using this local user account when you run the test controller configuration tool.

    I believe you are under case 1, if so make sure that the user you are setting up to run the test controller is either a member of the [Project Collection]\Project Collection Test Service Accounts group or the Project Collection Administrators group. 

    Make sure you have registered your Test Controller with a Team Project Collection before moving on to install the Test Agent. 

    To install a test agent, you must be a member of the Administrators security group on the computer.

    2. Now coming down to installing Test Agent. 

    - If you want to use the IntelliTrace collector or the network emulation, the user account must be a member of the Administrators group.

    - If the agent user name is not a member of the TeamTestAgentService group it will be added to this group, which requires permissions on the test controller machine.

    The user for the interactive process must be a member of the TeamTestAgentService security group or the process will not be able to run the tests assigned by the controller.

    Try click on configure and see if it works?

    Since the test controller has been registered with the team project the test agents should be registered with the test controller without any issues. Make sure that in the text box where you have to specify the test controller name, you key in the correct test controller name and port number, for example MachineName:6901 if you chose the defaults while installing the test controller.

    Since you are installing both the agent and the controller on the same machine i don't see any issues that may be caused by the firewall. Yet you can try disabling the firewall temporarily on the machine if the configuration fails. 

    See this msdn article for more details => http://msdn.microsoft.com/en-us/library/dd648127.aspx#Security

    HTH
    Cheers, Tarun 

     


    Please remember to mark the replies as answers if they help.

    Tarun Arora

     

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader


    Sunday, October 30, 2011 10:09 PM
  • Thank you very much Tarun for the response, Is it mandatory to register test controller with Team Project Collection . The documentation at http://msdn.microsoft.com/en-us/library/dd648127.aspx#Security includes administering test controller not registered with TFS.

     

    Thanks,
    Ramesh V

     

    Sunday, October 30, 2011 11:56 PM
  • Hi ramesv,

     

    1.       About this issue” Is it mandatory to register test controller with Team Project Collection?”

     

    To determine whether register TFS or not, it depends on whether you’ want to use TFS resource, like MTM or Lab Management

     

    2.       Based on your description, when you register the test agent with the test controller, it generated this issue. So I think you could check.

     

    (1)    Make sure you are a local administrator on the test controller machine, and that the Windows Firewall closed.

    (2)    Under the controller name you should write the <machineName>:port and not serviceName:port.

    (3)    A reboot is still required for the actual configuration to be successful. See

    http://social.msdn.microsoft.com/Forums/en-AU/windowsazureconnectivity/thread/4502f378-cf47-4e67-bc15-5a5795d23d4d

     

    Similar threads:

    http://social.msdn.microsoft.com/Forums/en/vststest/thread/105b565f-2423-4559-b2e4-61cb8950808f

    http://social.msdn.microsoft.com/Forums/fi-FI/vststest/thread/492b3585-2795-49ee-96fb-9af22de5ccb4

     

    Thanks,


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, November 2, 2011 3:43 AM
    Moderator