TF400917: The current configuration is not valid for this feature.

Question

Today I updated our work item so that they are 100 % conform to MSF for Agile Software Development 6.0.

Unfortunately my board on Team Web Access doesn't work anymore. Instead it shows this error:

TF400917: The current configuration is not valid for this feature.

So I also adapted the CommonConfiguration.xml that looks now that way:

<?xml version="1.0" encoding="utf-8"?>
<CommonProjectConfiguration>
  <TypeFields>
    <TypeField refname="System.AreaPath" type="Team" />
    <TypeField refname="Microsoft.VSTS.Scheduling.RemainingWork" type="RemainingWork" format="{0} h" />
    <TypeField refname="Microsoft.VSTS.Common.StackRank" type="Order" />
    <TypeField refname="Microsoft.VSTS.Scheduling.StoryPoints" type="Effort" />
    <TypeField refname="Microsoft.VSTS.Common.Activity" type="Activity" />
    <TypeField refname="Microsoft.VSTS.Feedback.ApplicationStartInformation" type="ApplicationStartInformation" />
    <TypeField refname="Microsoft.VSTS.Feedback.ApplicationLaunchInstructions" type="ApplicationLaunchInstructions" />
    <TypeField refname="Microsoft.VSTS.Feedback.ApplicationType" type="ApplicationType">
        <TypeFieldValues>
            <TypeFieldValue value="Web application" type="WebApp" />
            <TypeFieldValue value="Remote machine" type="RemoteMachine" />
            <TypeFieldValue value="Client application" type="ClientApp" />
        </TypeFieldValues>
    </TypeField>
  </TypeFields>
  <RequirementWorkItems category="Microsoft.RequirementCategory" plural="Stories">
    <States>
      <State value="New" type="Proposed" />
      <State value="Active" type="InProgress" />
      <State value="Resolved" type="InProgress" />
      <State value="Closed" type="Complete" />
    </States>
  </RequirementWorkItems>
  <TaskWorkItems category="Microsoft.TaskCategory">
    <States>
      <State value="New" type="Proposed" />
      <State value="Active" type="InProgress" />
      <State value="Closed" type="Complete" />
   <State value="Removed" type="Complete" />
    </States>
  </TaskWorkItems>
  <BugWorkItems category="Microsoft.BugCategory">
   <States>
       <State value="Active" type="InProgress" />
       <State value="Resolved" type="Resolved" />
       <State value="Closed" type="Complete" />
      </States>
  </BugWorkItems>
  <FeedbackRequestWorkItems category="Microsoft.FeedbackRequestCategory" plural="Feedback Requests">
    <States>
      <State value="Active" type="InProgress" />
      <State value="Closed" type="Complete" />
    </States>
  </FeedbackRequestWorkItems>
  <FeedbackResponseWorkItems category="Microsoft.FeedbackResponseCategory" plural="Feedback Responses">
    <States>
      <State value="Active" type="InProgress" />
      <State value="Closed" type="Complete" />
    </States>
  </FeedbackResponseWorkItems>
  <Weekends>
    <DayOfWeek>Saturday</DayOfWeek>
    <DayOfWeek>Sunday</DayOfWeek>
  </Weekends>
</CommonProjectConfiguration>

But it still doesn't work. How can I find out what's the reason for my problem? Is there somewhere a log that gives me more information?

Answer 1

Hi Thomas, 

Thanks for your post.

You’re using TFS 2012?

How did you update your work item? Did your board page works fine before you updated the work item?

Did you edit your work item type? 

Other Agile team project’s board pages work fine in TFS Web Access?

Please provide more information about this scenario. If you have any further research of this issue, please share your experience here.

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Yes, I'm using TFS 2012. I migrated recently from TFS 2010. After the migration everything was working fine, also the TFS Web Access.

I updated my work items by using a WIT that was created by a new team project based on MSF for Agile Software Development 6.0. I fear that's the reason for my troubles.

Answer 3

Hi Thomas, 

Thanks for your reply.

How did you update your work items using an Agile 6.0 WIT? Please provide the detailed steps here.   

I think you should update the WIT in your current team project(from TFS 2010) first, or import the Agile 6.0 WIT as the new work item type to your current team project, then edit the work items in your team project.   

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 4

ok, so these are the steps I did:

1. migrate TFS from 2010 to 2012

2. to activate all features in team web access I had to configure the work items (bug and user story) so that they have a "New" state. Also I had to configure the element "RequirementWorkItems" in the CommonConfiguration.xml. After these steps everything worked well and we were able to work with TFS 2012.

3. I created a new team project based on MSF for Agile Software Development 6.0. From this team project I exported the WIT.

4. In my currenty team project I imported these WITs.

E.g. when working with Work Items in Visual Studio 2010 (and 2012) everything looks fine. I also can access the work items in Team Web Access. Only when opening the "Board" in Team Web Access I get the mentioned error message.

Answer 5

Hi Thomas, 

Thanks for your reply.

Have you did some changes on your bug or user story work item type to make them can display under board page? 

Which WIT you exported from Agile 6.0 team project and imported it to your current team project?

Additionally, you can refer to the discussions in this post: http://social.msdn.microsoft.com/Forums/en-US/tfsprocess/thread/5d760572-8682-4970-baa3-d102992b395b or in this article: http://osnabrugge.wordpress.com/2013/01/04/changing-the-product-backlog-in-tfs-2012/.

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us
Develop and promote your apps in Windows Store
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 6

Hi John!

Finally I changed all of my WITs manually so that they have the same structure as Agile 6.0.

Now it works.

Thx