TF401009 and TF400997 errors during scheduled backups

by XDK 2. November 2014 03:50

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.

Tags:

TFS 2013

I don’t see MS Build logging verbosity property in TFS 2013 build definition

by XDK 1. November 2014 08:47

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

 

Tags:

Team Build | TFS 2013

TF221122: Error While Processing TFS OLAP Cube

by XDK 1. October 2014 11:44

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.

Tags:

SQL Analysis Services | TFS 2013

The number of items on your backlog exceeds the configured limit of 500

by XDK 29. April 2014 19:29

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"

Tags: ,

Azure DevOps on-premises | TFS 2012 | TFS 2013

Difference between Visual Studio Scrum 2013 and Visual Studio Scrum 2013.2 Process Template

by XDK 24. April 2014 19:46

Explanation:

  • Visual Studio Scrum 2013.2 Process Template has support for Shared Parameters which will enable testers the ability to manage test parameter data centrally. New Shared Parameter work item type, category, and link type are updated to the process template.
  • The ProductBacklog.wiq and SprintBacklog.wiq queries have been removed

Tags:

TFS 2013

About the author

My name is Xavier Dilip Kumar Jayaraj having 13+ years of IT experience which includes solid experience and depth Knowledge in Application Life Cycle Management, Configuration Management, Implementation and Support using TFS on-premises and Azure DevOps. I have invested in gaining DevOps knowledege to expertise with Cloud Computing providers namely Microsoft Azure and Amazon Web Services in recent years. I am very positive to learn and adapt emerging technologies to client’s environment.

Microsoft Certified: Azure Administrator Associate

Microsoft Certified: Azure DevOps Engineer Expert

DevOps Engineer Certificate Program | Transcript 

OTP-AWSD5: AWS IoT: Developing and Deploying an Internet of Things

[PCEP-30-01] PCEP – Certified Entry-Level Python Programmer

Quotes I Like

"Failure will never overtake me if my determination to succeed is strong enough."  - Dr. APJ. Abdul Kalam

"Always be yourself, express yourself, have faith in yourself, do not go out and look for a successful personality and duplicate it." - Bruce Lee

"Technology is just a tool. In terms of getting the kids working together and motivating them, the teacher is the most important." - Bill Gates

"Innovation distinguishes between a leader and a follower." - Steve Jobs

CategoryList

Disclaimer

The information provided here is based on my expreriences, troubleshooting and online/offline findings. It can be used as is on your own risk without any warranties and I impose no rights.