Exception:

TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration

Explanation:

After adding a initial state New to  Bug work item workflow, the backlog and the task board showed the error:

TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration

Solution:

1. Export team project's CommonConfiguration.xml

witadmin exportcommonprocessconfig /collection:<Collection URL> /p:<Team Project Name> /f:<CommonConfiguration.xml>

2. Add the new state to CommonConfiguration.xml's BugCategory

  <BugWorkItems category="Microsoft.BugCategory">

    <States>

      <State type="Proposed" value="New" />

      <State type="InProgress" value="Active" />

      <State type="Complete" value="Closed" />

      <State type="Resolved" value="Resolved" />

    </States>

  </BugWorkItems>

3. Import the updated CommonConfiguration.xml to team project

witadmin Importcommonprocessconfig /collection:<Collection URL> /p:<Team Project Name> /f:<CommonConfiguration.xml>

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:

Here