by Xavier Dilip Kumar
26. February 2016 13:54
Solution:
You may query the TFS cube thru excel to pull the information. Select the fields and configure as shown in the below screenshot.

by Xavier Dilip Kumar
18. February 2016 09:13
Explanation:
AcceptYours - Local version is to be used for merge
AcceptTheirs - Server version is to be used for merge
AcceptMerge - Resolve conflict by doing manual merge
by Xavier Dilip Kumar
5. February 2016 11:57
Explanation:
Visual Studio 2010 can't use the local workspaces created using Visual Studio 2012 or higher versions. The local workspace feature was introduced starting Visual Studio 2012.
Solution:
Create the workspace using Visual Studio 2010 to share or use the same workspace across Visual Studio 2010 and higher versions.
by Xavier Dilip Kumar
11. January 2016 12:49
Solution:
"Find by Status" and "Find by Wildcard" plug-ins are from TFS power tools. You need to install TFS power tools to gain access to "Find by Status" and "Find by Wildcard" menus.
by Xavier Dilip Kumar
31. December 2015 09:30
Exception:


Explanation:
This exception may appear when the lab environments exist with no lab systems.
Workaround:
- Open Microsoft SQL Server Management Studio.
- Connect to the TFS collection database where your team project exist.
- Run the following SQL query to identify the lab environments with no lab systems:
Select le.LabEnvironmentId from LabEnvironment le where le.PartitionId = 1 And NOT EXISTS (Select * From LabSystem ls where ls.LabEnvironmentId = le.LabEnvironmentId AND ls.PartitionId = 1)
- Note the Id's of the lab environment with no lab systems.
- Remove all lab environments with no lab systems, by using the following SQL command for each lab environment IDs:
Exec DeleteLabEnvironment @PartitionId = 1, @labEnvironmentId = <Lab Environment ID>, @namespaceGuid = N'9E4894C3-FF9A-4EAC-8A85-CE11CAFDC6F1', @deleteTestMachines = 1, @pendingOperationId = Null
a00ee40d-a650-425a-a1e6-6b24d7ac8141|0|.0|dfbc0555-1b48-4161-aee5-caf6951519e5
Tags: TFS2012
TFS | TFS 2012
by Xavier Dilip Kumar
31. December 2015 09:09
Exception:

Explanation:
The “Bug on the Backlog” feature is invalid for the projects that uses scrum process template. Bugs have always been on the backlog for scrum teams. This feature will be enabled or valid only for the projects created using MSF Agile and MSF CMMI process templates.
6965bd4b-4903-4eae-bc6f-cdd2d85e44dc|0|.0|dfbc0555-1b48-4161-aee5-caf6951519e5
Tags: TFS 2013
TFS | TFS 2013
by Xavier Dilip Kumar
23. December 2015 22:08
Solution:
Execute the following SQL script on the Tfs_Configuration database to remove the SCVMM setting:
Update [Tfs_Configuration].dbo.tbl_RegistryItems set RegValue = ' ' where ChildItem like 'VmmServerName%'
Update [Tfs_Configuration].dbo.tbl_RegistryItems set RegValue = ' ' where ChildItem like 'DnsSuffix%'
Update [Tfs_Configuration].dbo.tbl_RegistryItems set RegValue = ' ' where ChildItem like 'IPBlock%'
by Xavier Dilip Kumar
17. December 2015 07:57
Solution:
Type the following command in the command line window.
net user /Domain <Domain Account ID>
6a1735d2-cb06-439a-9346-4261f258b1e3|0|.0|dfbc0555-1b48-4161-aee5-caf6951519e5
Tags: Commands
General
by Xavier Dilip Kumar
16. December 2015 18:06
Exception:
TF208101: You cannot access the Analysis Services database because you have specified alternative credentials and you do not have permission on your computer to impersonate another user
Explanation:
The TF208101 error occur when trying to create Excel Reports from a TFS query using Visual Studio IDE
Solution:
- Right-click the visual Studio IDE icon or shortcut, and then click Run as administrator.
- Export the work item query to excel.
by Xavier Dilip Kumar
9. December 2015 08:53
Explanation:
You may experience "User Story" (MSF Agile template) or "Product Backlog Item" (Scrum template) or "Bug" (Scrum template) work item templates take long time to save when added to "Requirement" category in TFS 2012. These work items save in no time when removed out of "Requirement" category.
Requirement category in scrum template
<CATEGORY refname="Microsoft.RequirementCategory" name="Requirement Category">
<DEFAULTWORKITEMTYPE name="Product Backlog Item" />
<WORKITEMTYPE name="Bug" />
</CATEGORY>
Requirement category in MSF agile template
<CATEGORY name="Requirement Category" refname="Microsoft.RequirementCategory">
<DEFAULTWORKITEMTYPE name="User Story" />
</CATEGORY>
Solution:
The mentioned behavior is a known issue. Hotfix available at https://support.microsoft.com/en-us/kb/2938788
dae5b64a-8a5e-49b6-be33-532f2daeac54|0|.0|dfbc0555-1b48-4161-aee5-caf6951519e5
Tags: TFS2012
TFS | TFS 2012