Updating environment fail
Welcome to the troubleshooting page for lab management in Visual Studio 2010.This is a repository of errors we have seen in different scenarios and the ways to fix it.You can either search for your error or browse by category.If your error is not on this list, please take a minute and report it to us by When Team Foundation Server(TFS) and Virtual Machine Manager(VMM) Server are installed on the same computer, lab management configuration fails if Network Service account is used as the Team Foundation Server Service account1.7 TF26017 Unable to configure SCVMM server for Lab Management in TFS Admin console 1.8 TF255231 Unable to change SCVMM server for Lab Management in TFS Admin console 1.9 TF261007 Attach of Project collection fails if Lab Management is configured in source TFSImporting a virtual machine template fails with the error: “VMM is unable to process one of the provided parameters for New-Hardware Profile.The parameter -Num Lock was passed in with the following value "NULL".Virtual environment creation fails in the "Customization" step with error "Windows could not parse or process the unattend answer file for pass[specialize].The settings specified in the answer file cannot be applied.The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]."Virtual environment creation fails with error: "Memory requirement of the virtual machine(s) exceeds the available host resources. Socket Exception (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 1.201Test agent connection to controller fails with the error TF267055: The machine is not ready to run tests because of the following error: Unable to connect to the controller on 'aseemb-tc.microsoft.com:6901'.
Resolve those errors, and then try the operation again"Test agent fails to start with the error "Could not register TCP channel: System. No authority could be contacted for authentication.The test agent doesn’t start on a machine because one or more dependencies failed to start.You observe the following error in the lab center in MTLM: TF267066: Test agent is not running on the machine. If that does not fix the error, then log in to the machine and make sure the 'Visual Studio Team Test Agent' service is running without any errors..The agent can connect to the controller but the controller cannot connect to the agent because of following reason: A connection attempt failed because the connected party did not respond properly after a period of time, or established connection failed because connected host has failed to respond TF267055: The machine is not ready to run tests because of the following error: Cannot connect to the controller on 'aseemb-tc.microsoft.com:6901'.
The lab service account available on this machine is not valid.Either the updated service account is not available on this machine or the service account is not updated on Team Foundation Server.Try to repair the testing capability and then wait several minutes.If you still observe this problem, contact your team project collection administrator.:8080/tfs/Default Collection.