Search

TFS 2012 Agile 6.1 template problem "An item with the same key has already been added." by VidasV

Closed
as Duplicate Help for as Duplicate

1
0
Sign in
to vote
Type: Bug
ID: 778725
Opened: 2/7/2013 3:17:37 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
When accesing workitem type User story and its field definitions through the TFS API from .net, if the project is based on Agile 6.1 template API throws error "An item with the same key has already been added." It is for workitem type User story.

The TFS server is cloud based *.visualstudio.com
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Team Foundation Server 2012

Steps to reproduce

Connect to TFS.API and try accesing projects (based on agile 6.1 template) work item user story and then access its field definitions

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

Error
An item with the same key has already been added.

Expected results

Field definition list
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/8/2013 at 5:30 PM
Hi Vidas,

This sounds like a known issue we've fixed in Quarterly Update 1 service pack. If you haven't installed QU1 yet, there's a workaround you may want to try:

Just delete the TFS cache on the machine where your custom app is running and try again. The cache files would be located at:

C:\Users\<USER>\AppData\Local\Microsoft\Team Foundation\2.0\Cache



Feel free to follow up with me at hakane /at/ ms dot com.

Thanks,
-Hakan Eskici
Team Foundation Server
Posted by Microsoft on 2/7/2013 at 10:47 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/7/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.