Exceptions:

TF401009: The TFS service account NT AUTHORITY\LOCAL SERVICE cannot access network shares.  Change to an account that can access the backup path.
TF400997: SQL Server service is running as NT AUTHORITY\NETWORKSERVICE. Please change this account to an account that can be accessed

Explanation:

Scheduled Backups end up with failure, when granted permissions for the NT AUTHORITY\LOCAL SERVICE and the NT AUTHORITY\NETWORKSERVICE accounts on the backup path.

WorkAround:

To run Scheduled Backups without errors, you have to change the JobAgent and the Sql Server service accounts to User account.

Explanation:

This feature is not available in TFS 2013.

Solution:

You can set the verbosity in build definition using MSBuild arguments section in process tab

/flp:verbosity="<verbosity>"

Following are the levels of verbosity that can be set for the ms build output:

· Quiet
· Minimal
· Normal
· Detailed
· Diagnostic

Exception:

After upgrading to TFS 2013, the TFS OLAP Cube fails processing with one of the following messages:

Invalid column name ‘System_AssignedTo__Name’.; 42S22;

Invalid column name ‘System_AssignedTo__SID’.; 42S22

Query execution failed for dataset ‘ds[Whatever]‘

Solution:

• In TFS Admin Console, look up the account under “Account for accessing data sources” under the “Analysis Services” tab (Reporting » Edit).
• In SQL Server, add that account to the Tfs_Warehouse database, to the TFSEXECROLE role.

Solution:

1. Open Visual Studio IDE  
2. Go to Tools --> Options in Visual Studio menu and open the options. Select Source Control --> Visual Studio Team Foundation Server and tick the option "Show deleted items in Source Control Explorer" and click OK.
3. Now you can see the deleted files appear in Source Control Explorer. Right click on the Folder/File you want to restore and click "Undelete" to get it restored.

Explanation:

The default display limit for the task board is 500 tasks.For performance reasons, the task board is restricted to display a maximum of 500 work items. When you open the task board, all work items are loaded into cache. so changing the limit increases the memory demand on your clients and might cause issues. Limiting the number of work items may yield quicker load times

Work Around:

You can modify the process template to increase the limit.

For TFS 2012, edit Agileprocessconfig.xml

For TFS 2013, edit ProcessConfiguration.xml

Step 1: Export Agileprocessconfig.xml from the team project

witadmin exportagileprocessconfig /collection:"http://tfs:8080/tfs/DefaultCollection"

 /p:DefaultProject /f:"c:\Agileprocessconfig.xml"

Step 2: Add a attribute "workItemCountLimit" to the <IterationBacklog> element as below

<?xml version="1.0" encoding="utf-8"?>
<AgileProjectConfiguration>
  <IterationBacklog workItemCountLimit="1000">
    <Columns>
      <Column width="50" refname="Microsoft.VSTS.Scheduling.Effort" />
      <Column width="400" refname="System.Title" />
      <Column width="100" refname="System.State" />
      <Column width="100" refname="System.AssignedTo" />
      <Column width="50" refname="Microsoft.VSTS.Scheduling.RemainingWork" />
    </Columns>
  </IterationBacklog>
  <ProductBacklog>
    <AddPanel>
      <Fields>
        <Field refname="System.Title" />
      </Fields>
    </AddPanel>
    <Columns>
      <Column width="400" refname="System.Title" />
      <Column width="100" refname="System.State" />
      <Column width="50" refname="Microsoft.VSTS.Scheduling.Effort" />
      <Column width="200" refname="System.IterationPath" />
      <Column width="200" refname="System.Tags" />
    </Columns>
  </ProductBacklog>
</AgileProjectConfiguration>

Step 3 : validate your Agileprocessconfig.xml

witadmin importagileprocessconfig /collection:"http://tfs:8080/tfs/DefaultCollection"

 /p:DefaultProject /f:"c:\Agileprocessconfig.xml" /v

 Step 4: Import Agileprocessconfig.xml to the team project

witadmin importagileprocessconfig /collection:"http://tfs:8080/tfs/DefaultCollection"

 /p:DefaultProject /f:"c:\Agileprocessconfig.xml"