Skip to main content

TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration.

One of my clients modified the TFS process template for one of their projects. They updated the bug Work Item and added some extra states. Everything seemed to work until they opened up the TFS Scrum board. Instead of a nice and fully functional Scrum board, they got the following error message:

TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration.

To fix this, I had to execute the following steps:

  • Export the CommonProcessConfig xml:

C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE>witadmin exportcommonprocessconfig /collection: <collectionurl> /p: <projectname> /f:c:\processconfig.xml

  • Update the BugWorkItems section inside the XML and add the missing states:
  • <BugWorkItems category="Microsoft.BugCategory">
        <States>
          <State type="InProgress" value="Not Done" />
          <State type="InProgress" value="On Hold" />
          <State type="Complete" value="Closed" />
          <State type="Complete" value="Not reproducable" />
          <State type="Complete" value="Release" />
          <State type="Resolved" value="Test AIG" />
          <State type="Resolved" value="Test BUS" />
          <State type="Resolved" value="Test Failed" />
        </States>
      </BugWorkItems>

    • Import the updated config again:

    C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE>witadmin importcommonprocessconfig /collection: <collectionurl> /p: <projectname> /f:c:\processconfig.xml

    And the issue was gone Glimlach

    Popular posts from this blog

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    .NET 8–Keyed/Named Services

    A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...