Exception:

Unable to read data from the transport connection: 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

Explanation:

The above exception pops up when doing a Get operation on a specific file in the build environment.

WorkAround:

Perform the following steps on your build agent by opening the Team Explorer\Visual Studio IDE.

Explanation:

You can query the list of TFS Jobs from the Tfs_Configuration database tbl_JobDefinition table

SELECT *  FROM [Tfs_Configuration].[dbo].[tbl_JobDefinition]

Using the Job Id, you can get the job execution details from the Tfs_Configuration database tbl_JobHistory table

SELECT * FROM [Tfs_Configuration].[dbo].[tbl_JobHistory] where [JobId] = 'XXX'

Following query gets the "Team Foundation Server Send Mail Job"  details

SELECT * FROM [Tfs_Configuration].[dbo].[tbl_JobHistory] where [JobId] = 'B1516502-4633-432B-BDB3-74C802C5F2B7' 

tbl_JobHistory table field details

1) Job ID – Every job in the system has a unique id.

2) Job Agent ID – Every AT/Job Agent has a unique id.  This field is useful if you have multiple application tiers and you want to know which one the job executed on so that you can investigate the event log or performance counters.

3) Result – This is an integer that represents the result of the job. 

   0 = Succeeded

   1 = PartiallySucceeded

   2 = Failed

   3 = Stopped

   4 = Killed

   5 = Blocked

   6 = ExtensionNotFound

   7 = Inactive

   8 = Disabled

4) Queued Reason – This is an integer that represents the way a job was scheduled. 

   0 = No reason to execute the job

   1 = Job has a schedule

   2 = Queued manually

   4 = Queued manually while already in progress

   8 = Queued due to previous result (Blocked, Inactive)

5) Start Time – The local time that the job started executing on a job agent

6) End Time – The local time that the job finished executing on a job agent

7) Duration – The number of minutes that the job was executing for

8) Result Message – Jobs are able to log a status message when they finish executing.

Others: 

How to process failed Jobs?

TFS Job details.

Exception:

Login failed for user XXX

Explanation:

I am not able to connect to TFS cube even though, I am in Tfs_Analysis --> TfsWarehouseDataReader's role. 

Solution:

Make sure that you have enabled the "Read definition" database permission for TfsWarehouseDataReader role

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"

Server side exceptions:

System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string.

Parameter name: startIndex

   at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)

   at Microsoft.TeamFoundation.Server.WebAccess.Routing.TfsRoute.GetRouteData(HttpContextBase httpContext)

   at System.Web.Routing.RouteCollection.GetRouteData(HttpContextBase httpContext)

   at System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context)

   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)

Explanation:

This error occurred while trying to access the TFS 2012 update 3 server team project website for viewing boards or creating PBIs, bugs and other work items. The error can be reproduced by clicking back and forth a few times between the home page and CODE, WORK, TEST, etc. The issue was specific to one specific collection in the server. 

Fix:

One of the team project's shared query with wrong condition clause was trying to load 73000+ WIs which was pinned to the Team Favorites in the home page causing the issue. The issue was resolved after correcting the query.