The Test Controller is not configured correctly
The information in this article applies to:
Visual Studio Team Foundation Server 2010
Visual Studio 2010 Lab Management
Windows Server 2003 and Windows Server 2008
Team Foundation Server Complete Health Check
Visual Studio Lab Management Health Check
The Best Practices Analyzer tool for Team Foundation Server checks the configuration of the Visual Studio Test Controller service on those servers where it is installed. The tool logs the information it gathers in the tree report under the Test Controllers node**.** You can locate the Test Controllers node by expanding Team Foundation Server Complete Health Check, expanding Team Foundation Server, expanding Team Project Collections, and then expanding a named project collection.
In order to use Lab Management, you must resolve all errors, which are indicated by the .gif "Error icon")
icon. You do not have to resolve warnings, which are indicated by the .gif "Warning icon")
icon.
An information message (.gif "Information icon")
) appears if the following condition is true:
No test controllers are registered with team project collection
To correct this condition, register at least one test controller with the named team project collection. For more information, see the following Microsoft Web sites: Installing and Configuring Visual Studio Agents and Configuring Lab Management for the First Time.
A warning message () appears if one of the following conditions is detected:
WMI access not available to test controllers
This condition could be caused by insufficient permissions granted to the user who is running the scan. To correct this condition, grant administrative privileges on the server where the test controllers are installed to the user who is running the scan.
For computers that are running Windows Server 2008, you might need to configure additional settings to handle remote connections under User Access Control (UAC). In addition, you might need to verify that the WMI traffic port is open on the server that hosts the library server. For more information, see Prerequisites for Using the Best Practices Analyzer Tool.
An error message () appears if the tool detects one of the following conditions:
The version of Test Controller is not compatible
You must install the same version of Visual Studio Test Controller as Team Foundation Server on the physical or virtual machine in order to use the test controller with Lab Management. For more information, see the following Microsoft Web sites: Installing and Configuring Visual Studio Agents and Configuring Lab Management for the First Time.
Test Controller service is not responding (Error)
Test Controller does not have appropriate permissions on the Team Foundation Server (Error)
Firewall exception is not added for the Test Controller (Error)
To use the testing integration capability, you must resolve all errors.
Test Controller service is not responding
The Visual Studio Test Controller service runs as a Windows Service on the computers on which it is installed. To resolve this error condition, determine if the service configuration is correct and restart the service.
To troubleshoot the test controller service
Perform one or more of the following actions:
Check the Event logs on the server where the test controller is running.
Verify that the test controller is correctly registered with a team project collection using the Test Controller Configuration Tool. For more information, see the following topic on the Microsoft Web site: How to: Add Test Controllers to Use for Testing with Lab Management.
Make sure that the Visual Studio Test Controller service is set to start automatically, and then restart the service. For more information, see A service is not running.
Test Controller does not have appropriate permissions on the Team Foundation Server
The Test Controller registered with the project collection does not have appropriate permissions on the Team Foundation Server. You must add the Visual Studio Test Controller service account to the Project Collection Test Service Accounts. For more information, see the following page on the Microsoft Web site: How to: Add Test Controllers to Use for Testing with Lab Management.
Firewall exception is not added for the Test Controller
A firewall exception has not been added for the test controller that is registered with the team project collection. If you are running Windows Firewall, make sure that the exception has been added for the test controller port. By default, the Visual Studio Test Controller service uses port 6901.
For more information, see the following pages on the Microsoft Web site: Installing and Configuring Visual Studio Team Agents: Install a Test Controller and How to Configure Windows Firewall on a Single Computer.