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

by Xavier Dilip Kumar 29. April 2014 19:29


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"?>
  <IterationBacklog workItemCountLimit="1000">
      <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" />
        <Field refname="System.Title" />
      <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" />

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: ,

TFS | TFS 2012 | TFS 2013

How to activate Shared Parameters feature on a team project upgraded from TFS 2013 to TFS 2013.2 update

by Xavier Dilip Kumar 24. April 2014 20:01


After updating TFS 2013 server with update TFS 2013.2, Shared Parameters feature need to be activated manually for each team project. This feature provides to testers and test leads the ability to manage test parameter data at one place by using Shared Parameters. Any subsequent changes to parameter data can be updated at one place and all the test cases referencing the Shared Parameter are automatically updated


  • Open team project web access.
  • Click on "Test" tab --> "parameters" option


  • Click on "Configure feature" option.


  • Click on "Verify" & "Apply" button

Tags: ,

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

by Xavier Dilip Kumar 24. April 2014 19:46


  • 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


TFS 2013

TF400898: An Internal Error Occured.

by Xavier Dilip Kumar 16. April 2014 19:18


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)


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. 


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.

Tags: ,

TFS | TFS 2012

Work item history display revision change even though no field values were updated

by Xavier Dilip Kumar 15. April 2014 13:36


  1. History displays all changes to Rev field through service account when iteration path nodes are modified
  2. Changed date and Changed by field values are updated automatically


This issue occur when we rename, move, or make any changes to the iteration path nodes in TFS web portal settings.

More Details


TFS 2012 | TFS 2013

After applying update 2, not able to connect to TFS 2013 server with Urban Turtle 4.16 installed

by Xavier Dilip Kumar 15. April 2014 06:20


Client exception: TF31002 : Unable to connect to this Team Foundation Server

Server exception:  Could not load type 'Microsoft.TeamFoundation.Server.WebAccess.Routing.SupportedRouteAreaAttribute' from assembly 'Microsoft.TeamFoundation.Server.WebAccess, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.


Looks like there are compatibility issues with Urban Turtle 4.16 or earlier with TFS 2013 Update 2. You will see the above exceptions, as soon as you apply update 2 on TFS 2013 server with Urban Turtle 4.16 installed.


You need to uninstall Urban Turtle 4.16 or earlier and install Urban Turtle 4.16.1. You will end up with the following error while uninstalling Urban Turtle 4.16 after applying Update 2. 

Urban Turtle 4.16 is not compatible with this version of Team Foundation Server 2013. Please make sure that you are running Team Foundation Server 2013 (RTM, build 21005.01) or download a compatible version from our website.

Workaround to uninstall Urban Turtle 4.16 or earlier: 

1. Use TFSServiceControl quiesce command to ensure that all necessary operations, services, and application pools are stopped for maintenance tasks

  • TFSServiceControl quiesce

2.Launch the Registry Editor (c:\windows\regedit.exe)

2.Navigate to key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TeamFoundationServer\12.0'

3.Double-click on the 'BuildNumber' entry

4.Change the value to 21005.01

5.Uninstall Urban Turtle 4.16

6.Restore the value of 'BuildNumber' back to '30324.00'

7. Use TFSServiceControl unquiesce command to start all necessary operations, services, and application pools for TFS

  • TFSServiceControl unquiesce 

8.Install Urban Turtle 4.16.1




TFS 2013

Build.targets (19): TF10131: The shelveset name _Build_XXXXX?queueId=XXXX contains more than 64 characters, contains one of the following characters: "/:<>\|*?; or ends with a space. Type a valid name and try again. Build.targets (19): The "Get" task failed unexpectedly.

by Xavier Dilip Kumar 14. April 2014 11:41


This error occurs when attempting a gated checkin following environment:

* TFS 2012 Update 3 or earlier updates application server

* TFS 2010 SP1 Build Server

* "UpgradeTemplate.xaml" used for build process


This is a known issue that has been fixed with TFS 2012 Update 4

Tags: , ,

TFS | TFS 2010 | TFS 2012

How to install TFS update on TFS Servers?

by Xavier Dilip Kumar 9. April 2014 20:32


1. Log on to your TFS App tier

Note : Make sure you had backed up all databases related to TFS before installing the update

2. Use TFSServiceControl quiesce command to ensure that all necessary operations, services, and application pools are stopped for maintenance tasks

  • TFSServiceControl quiesce

3. Install the update.

4. Run the TFS Admin console tool to configure the TFS App Tier for installed update.

5. Use TFSServiceControl unquiesce command to start all necessary operations, services, and application pools for TFS

  • TFSServiceControl unquiesce 

If you have multiple app tier(s), proceed with step 1 to 3 on each app tier one by one first and then proceed with step 4 and 5 on each app tier one by one.

Tags: ,

TFS 2012 | TFS 2013

About the author

My name is Xavier Dilip Kumar Jayaraj and I am a Software Configuration Management Engineer with a background in application development, Build & packaging using Install Shield.

Profile in LinkedIn


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


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.

Month List