1. Running remote tests from Team Foundation Build fail with the following error: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond."
Details: When you run remote tests from Team Foundation Build, the user account used to run the build must be a member of the TeamTestControllerUser or TeamTestControllerAdmins local security accounts on the Team Test Load Agent controller computer. Also, if you use Windows Firewall (or another third-party firewall solution), MSBuild must be able to access remote computers.
Workaround: Add the user account used to run the build to the TeamTestControllerUser or TeamTestControllerAdmins local security account on the Team Test Load Agent controller computer. Also, add MSBuild to the Windows Firewall exception list on the Team Foundation Build computer.
2. Some features related to Team Foundation Build stop working after changing the Team Build Service account.
Details: If you change the account used to run the Team Build Service, you must grant the new user account some additional permissions.
Workaround: The Team Build Service account needs write permissions to the ASP.NET temp folder on the build computer.
3. Team Foundation Build operations fail when a team project is deleted and created again with the same name.
Details: If you delete an existing team project on Team Foundation Server, and then create a new team project with the same name, you will be unable to create new build types. This problem occurs because data in the local cache is not updated when the team project is deleted.
Workaround: Restart Visual Studio on the computer where you experience this issue. Or reset IIS on the application-tier computer by running iisreset at the Command Prompt window.
No comments:
Post a Comment