Explanation:

1. Download the latest Cross-Platform Command-Line Client from the below link

   https://www.microsoft.com/en-us/download/details.aspx?id=47727

2. Unzip the archive file that contains the client.

3. Configure your shell or system path to include the folder to which you unzipped the archive.

vi ~/.bash_profile

export PATH=$PATH:<Path of the Command-Line client unzipped folder>

4. Save and exit        

5. Execute the below command

source ~/.bash_profile

tf eula -accept

6. At command prompt, type tf, and then press the ENTER key.

Optional:

7. Set the TF_AUTO_SAVE_CREDENTIALS environment variable to any value, such as "1" to save TFS credentials in the credentials cache. After you set the variable, you do not need to specify authentication information each time that you run a tf command.

8. execute the below command

vi ~/.bashrc 

9. Add the line

export TF_AUTO_SAVE_CREDENTIALS=1

10. Save and exit

11. Execute the below command

    source ~/.bashrc

tf get -login:<User name>,<Password>

Exception:

TF400018: The local version table for local workspace <Box Name;User Name> could not be opened. The workspace version table contains as unknown scheme version.

Explanation:

This error may occur when the local workspace is corrupted

Workaround:

Delete or rename the local workspace cache folder at "C:\ProgramData\Microsoft\Team Foundation"

Exception: 

Solution:

This error may occur when the Test Controller and Agents runs out disk space. Try to clean up the disk to gain free space or add extra space to the drive. 

Explanation:

You can build the Visual Studio 2012 later versions in TFS 2012 build environment by configurating the 'ToolPath' property in the TFS 2012 build xaml file.

Solution:

Open the TFS 2012 build xaml file with the same Visual Studio version (i.e VS 2012) to edit the 'ToolPath' property as below and save the xaml to build.

Visual Studio 2012 ToolPath

On 32-bit machines : C:\Program Files\MSBuild\12.0\bin
On 64-bit machines : C:\Program Files (x86)\MSBuild\12.0\bin

Visual Studio 2015 ToolPath
On 32-bit machines : C:\Program Files\MSBuild\14.0\bin
On 64-bit machines : C:\Program Files (x86)\MSBuild\14.0\bin

Workaround:

• Delete the registered build process template in the collection database

          use <Collection database>;
          delete from tbl_BuildProcessTemplate where ProcessTemplateID = 'updated Process Template ID';

• Create the build definition again