Troubleshooting Testing Capability

[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]

This topic describes some common problems you might encounter when you run tests on virtual environments and offers some suggestions for solving them.

  • Testing capability status becomes ‘Failed’ or stays ‘Partially Ready’ when the virtual machines in the environment are up and running.

    This indicates a problem in communication between the test controller and the test agents in the virtual machines. As a result, you cannot run manual or automated tests on the virtual environment. This status is accompanied by an error or warning message in Microsoft Test and Lab Manager or Microsoft Environment Viewer. In most cases, the error message indicates what is wrong and how to fix it. Perform the steps, and then click Try Again. The following is a list of common errors and troubleshooting steps:

    1. Missing permission on the test controller: The account under which the test agents in the virtual machines are configured should be added to the local group ‘TeamTestAgentService’ on the test controller machine. If the test agent is running under a local account, then create a local account with the same username/password on the test controller

    2. Missing local account: If the test controller service is running under a local account, you must create a local account that uses the same user name and password on every machine where the test agent is installed.

    3. An error occurred while processing the request on the server: System.IO.IOException: If hotfix KB968389 (part of Windows update) is installed on your test agent or test controller machine, they cannot communicate and return this error. You must uninstall this hotfix manually and restart the machine.

    4. Missing lab agent: Verify that the lab agent is installed and running by opening Windows Services Manager in each virtual machine and looking for Visual Studio Team Lab Management Agent Service.

    5. Network connection: Ensure that there is good network connectivity between the virtual machines and the test controller machine.

    6. Incorrect test agent or controller configuration: To determine whether you have configured the test agent correctly on a virtual machine, run the following command: test_agent_install_location\testagentconfig.exe verify.

      Similarly, to check if you have configured the test controller correctly, run the command: test_controller_install_location\testcontrollerconfig.exe verify.

  • Testing capability status is not ‘Ready’ for machines on which you have configured the test agent to run as an interactive process.

    If you have configured the test agent to run as an interactive process, it will start to run only after you log on to the machine with the credentials you configured the test agent. You can verify and monitor the status of the test agent running as an interactive process through the notification area application.