How to enable test controller logs

Here are the steps which you should perform to enable test controller logs. 1. Go to your test controller installation directory (typically it is something like C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\). 2. Open the controller configuration file (QTController.exe.config) and change the trace level to 4 and enable the trace listener as shown below:   <system.diagnostics>   …

8

How to create ‘testing enabled’ lab environment

In this post, I plan to talk about how you can create ‘testing enabled’ lab environment. I am assuming that you have already configured lab management and have a ‘lab ready virtual machine’ in your SCVMM library, but if you have not done any of that, please do that as mentioned in the first 2…

0

Authentication failed on the remote side (the stream might still be available for additional authentication attempts). No authority could be contacted for authentication.

In Visual Studio Team Lab Management, the following error message is observed on a testing capability enabled lab system when the lab system had lost trust relationship with the domain. TF267055: The machine is not ready to run tests because of the following error: Unable to connect to the controller on ‘aseemb-tc.fareast.corp.microsoft.com:6901’. The agent can…

0

Error starting the test run: Build directory of the test run is not specified or does not exist.

In Microsoft Test and Lab Manager, the above error message is observed during the execution of an automated test run on a test controller. It can occur in either of the following conditions. 1. The account under which test controller is running does not have read permission on the build directory. (The build directory is…

10

System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.22.221.228:6901

In Visual Studio Team Lab Management Beta2, the above error message is normally observed on a testing capability enabled lab environment/lab system when firewall service is blocking the calls to test controller. To resolve this, ensure that firewall exception for test controller is added properly in the firewall exception list.

0

Could not register TCP channel: System.Net.Sockets.SocketException (0x80004005): Only one usage of each socket address (protocol/network address/port) is normally permitted

I have observed the above error message a couple of times on windows xp machines when the test agent service is restarted. The service does not start due to this error and in test agent log file following stack trace is observed. ASEEMB-SPEARHEA\QTAgentService.exe, AgentService: Could not register TCP channel: System.Net.Sockets.SocketException (0x80004005): Only one usage of…

0