Share via

Issues with Test agent configuration with Test controller

  • Article

Deepak Mittal, Support Escalation Engineer, brings us this support experience today.... 

Problem Description:

You may face problem with Test agent configuration with Test controller.

 Resolution:

If you face issue with test agent configuration with controller and error message is something like "no agent <machinename> exists, Then the possible solution for you is:

 
•Use the BindToproperty in the controller and agent config file as mentioned in below KB article:

support.microsoft.com/kb/944496

 Possible Cause:

This issue may occur in case you have multiple network adapter.

 
Please note that after following the above steps, you may get the same error when you run the test.

 Suggestion for solving that:

In hosts file on agent first entry is [127.0.0.1 <machinename>], so agent try to set machine name in controller, which is not accessible from controller.

Hence, in order to resolve it, put the FQDN of agent with 127.0.0.1 as first entry in host file of agent and then try out pinging the agent’s FQDN specified in previous step from controller, if successful then test will run fine, if not then add an entry of agent’s FQDN with actual IP controller machine’s hosts file.