FIX: "No such host is known" error message when you run a load test on a test agent and a test controller in Visual Studio Team Agents 2010

Applies to: Visual Studio Team Agents 2010Microsoft Visual Studio 2010 Service Pack 1Visual Studio 2010 Ultimate

Symptoms


Consider the following scenario:
  • You create a load test in Microsoft Visual Studio Team Agents 2010.
  • On one computer, you configure a test controller in a domain.
  • On another computer, you configure a test agent in a different domain.

    Note The two domains trust one another. 

  • You run the load test on the test controller computer and the test agent computer.
In this scenario, the test controller cannot connect to the test agent. Additionally, you receive the following error message:

System.Net.Sockets.SocketException (0x80004005): No such host is known

Cause


This issue occurs because the test agent computer sends its Network Basic Input/Output System (NetBIOS) name instead of sending its Fully Qualified Domain Name (FQDN) name to the test controller computer. When the DNS server of the test controller computer does not have the IP address mapping of the NetBIOS name of the test agent computer, the issue that is described in the "Symptoms" section occurs.

Resolution


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have Visual Studio 2010 Service Pack 1 (SP1) installed.

Restart requirement

You do not have to restart the computer after you install the hotfix. However, you must restart the test controller services and test agent services.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Leviewer.exe10.0.40219.385118,5448-Mar-129:39x86
Microsoft.teamfoundation.build.client.dll10.0.40219.385436,5526-Mar-128:03x86
Microsoft.teamfoundation.build.conTrols.dll10.0.40219.3851,365,3288-Mar-129:39x86
Microsoft.teamfoundation.client.dll10.0.40219.3851,595,7046-Mar-128:03x86
Microsoft.teamfoundation.common.dll10.0.40219.385525,6246-Mar-128:03x86
Microsoft.teamfoundation.common.library.dll10.0.40219.385335,1846-Mar-128:03x86
Microsoft.teamfoundation.conTrols.dll10.0.40219.385938,8168-Mar-129:39x86
Microsoft.teamfoundation.dll10.0.40219.385675,6326-Mar-128:03x86
Microsoft.teamfoundation.lab.activities.dll10.0.40219.385772,9448-Mar-129:39x86
Microsoft.teamfoundation.lab.client.dll10.0.40219.385153,4086-Mar-128:03x86
Microsoft.teamfoundation.lab.uiutils.dll10.0.40219.385267,0808-Mar-129:39x86
Microsoft.teamfoundation.lab.workflow.activities.dll10.0.40219.385440,6728-Mar-129:39x86
Microsoft.teamfoundation.officeintegration.common.dll10.0.40219.385376,1608-Mar-129:39x86
Microsoft.teamfoundation.officeintegration.project.dll10.0.40219.385517,4808-Mar-129:39x86
Microsoft.teamfoundation.sync.mapping.dll10.0.40219.38572,5208-Mar-129:39x86
Microsoft.teamfoundation.sync.provisioning.dll10.0.40219.385194,3848-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.activities.common.dll10.0.40219.385315,2488-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.activities.dll10.0.40219.3851,512,2968-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.activityruntime.dll10.0.40219.385220,0168-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.client.dll10.0.40219.385685,4086-Mar-128:03x86
Microsoft.teamfoundation.testmanagement.client.Themes.dll10.0.40219.3853,059,5608-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.client.wpfconTrols.dll10.0.40219.385257,9128-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.clientpackage.dll10.0.40219.38574,0888-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.common.dll10.0.40219.38534,6566-Mar-128:03x86
Microsoft.teamfoundation.testmanagement.conTroller.dll10.0.40219.385120,6808-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.conTrols.dll10.0.40219.385494,4328-Mar-129:39x86
Microsoft.teamfoundation.testmanagement.conTrols.wpfworkitemconTrols.dll10.0.40219.385100,2328-Mar-129:39x86
Microsoft.teamfoundation.versionconTrol.client.dll10.0.40219.385706,4006-Mar-128:03x86
Microsoft.teamfoundation.versionconTrol.common.dll10.0.40219.385233,3126-Mar-128:03x86
Microsoft.teamfoundation.versionconTrol.conTrols.dll10.0.40219.3854,439,3928-Mar-129:39x86
Microsoft.teamfoundation.workitemTracking.client.dll10.0.40219.385699,2326-Mar-128:03x86
Microsoft.teamfoundation.workitemTracking.conTrols.dll10.0.40219.3851,215,3368-Mar-129:39x86
Microsoft.teamfoundation.workitemTracking.proxy.dll10.0.40219.385391,0086-Mar-128:03x86
Microsoft.visualstudio.qualitytools.agentobject.dll10.0.40219.385106,8488-Mar-129:39x86
Microsoft.visualstudio.qualitytools.common.dll10.0.40219.3851,355,6008-Mar-129:39x86
Microsoft.visualstudio.qualitytools.conTrollerobject.dll10.0.40219.385276,3288-Mar-129:39x86
Microsoft.visualstudio.qualitytools.datacollectionagentobject.dll10.0.40219.38537,2488-Mar-129:39x86
Microsoft.visualstudio.qualitytools.executioncommon.dll10.0.40219.385481,6408-Mar-129:39x86
Microsoft.visualstudio.qualitytools.resource.dll10.0.40219.385967,0008-Mar-129:39x86
Microsoft.visualstudio.qualitytools.testcasemanagement.dll10.0.40219.3851,280,3688-Mar-129:39x86
Microsoft.visualstudio.qualitytools.tmi.dll10.0.40219.385398,6728-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.build.dll10.0.40219.385142,6808-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.dll10.0.40219.38594,0248-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.teamexplorer.dll10.0.40219.385800,1048-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.versionconTrol.dll10.0.40219.38559,2488-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.versionconTrol.dll10.0.40219.38559,7608-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.versionconTrol.dll10.0.40219.38561,2968-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.versionconTrol.dll10.0.40219.38563,8568-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.versionconTrol.dll10.0.40219.385940,3928-Mar-129:39x86
Microsoft.visualstudio.teamfoundation.workitemTracking.dll10.0.40219.385461,1688-Mar-129:39x86
Microsoft.visualstudio.teamsystem.integration.dll10.0.40219.385193,3688-Mar-129:39x86
Microsoft.visualstudio.testtools.manualtest.common.dll10.0.40219.385813,4168-Mar-129:39x86
Microsoft.visualstudio.testtools.uitest.extension.ie.dll10.0.40219.385251,2408-Mar-129:39x86
Microsoft.visualstudio.testtools.uitest.extension.uia.dll10.0.40219.385107,3688-Mar-129:39x86
Msdiff.dll10.0.40219.385485,6408-Mar-129:39x86
Mtm.exe10.0.40219.385449,2808-Mar-129:39x86
Qtagent.exe10.0.40219.38521,2568-Mar-129:39x86
Qtagent.exe10.0.40219.38521,2648-Mar-129:39x86
Qtagent32.exe10.0.40219.38521,2648-Mar-129:39x86
Qtagent32.exe10.0.40219.38521,2728-Mar-129:39x86
Qtagentservice.exe10.0.40219.385100,1208-Mar-129:39x86
Tf.exe10.0.40219.385325,8888-Mar-129:39x86

Workaround


To work around this issue, use one of the following methods:
  • Update the DSN server of the test controller computer to map the IP address to the NetBIOS name of the test agent computer.
  • Add a manual entry to the host file of the test controller computer to resolve the NetBIOS name of the test agent computer.

More Information


After apply this hotfix, you must enable the test controller and the test agent to communicate with the FQDN name instead of NetBIOS name. To do this, edit the following files:
  • Add the <add key="UseNetBiosName" Value="0"> appSettings element to the <Controller Install Directory>\Common7\IDE\QTController.exe.config host file on the test controller computer.
  • Add the <add key="UseNetBiosName" Value="0"> appSettings element to the <Agent Install Directory>\Common7\IDE\QTAgentService.exe.config host file on the test agent computer.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.