Tim Elhajj

Off the Microsoft stack!

Run the Configure Features Wizard


The Configure Features wizard helps you add features to your pre-existing projects. If you have not customized your team project, or only slightly customized it, it can add features automatically for you. If you have customized your team project or process templates extensively, you will probably not be able to use the wizard.

You can use the wizard to:

  • analyze projects to determine if they can be automatically updated with available features
  • automatically configure these projects with those features, such as review, feedback, and planning tools

The wizard provides information about your project and the changes it will make in each step. Depending on how much you have customized your team project, you might need to choose between process templates. In some cases, no automatic configuration is possible, and you must manually make the changes required to enable the features you want. Unless you have heavily customized your project or templates, however, the wizard will be able to upgrade your project for you, providing you access to all the neat new features for this release, such as:

  • Code Review: Initiate and track code review requests and responses.
  • Feedback: Initiate feedback requests and track feedback responses.
  • My Work: Organize upcoming, ongoing, and suspended work.
  • Planning Tools: Manage the product backlog and plan and run sprints using the backlog page, iteration pages, capacity setting, and task board page.
  • Storyboard Linking: Access the latest version of storyboards by linking them to work items.
  • Hidden Types Category: Specify the set of work item types that users should create through a form or tool, and not manually. By default this includes Code Review Request and Code Review Response, Feedback Request and Feedback Response, and Shared Steps.
Required Permissions

In case you hadn’t guessed already, you must be at least a member of the Project Administrators group to configure features for a project, or have the equivalent permissions. Collection admins and Team Foundation admins can do this too. Regular project members…not so much.

To run the Configure Features wizard

  1. Open Team Web Access and choose the team project you want to update. (If you’re not sure how to open a project in Team Web Access, it’s easy; just open a web browser and navigate to the URL of your team project, using the http://ServerName:Port/tfs/CollectionName/ProjectName format.)
  2. Choose the  gear icon to open the administration page, and then choose Configure Features.

    If Configure Features doesn’t appear, either your project has already been updated with all features available, or else you don’t have the required permissions to configure features.  Assuming there are features to configure and you have the right permissions, the Configure Features wizard opens and lists those features not yet configured for your team project:
  3. Choose Verify to determine if the listed features can be configured automatically for your project.
  4. After the verification process completes, choose from one of these options, depending on what the wizard returns:
    • Configure:  to proceed with the automatic update, disregarding any exceptions listed.
    • Cancel: to close the wizard as you want to update a customized process template or manually update the team project.
    • Choose a process template to continue: if you are asked to choose between two or more potential matches, to pick the process template that best matches the template used to create your team project, and then proceed with the configuration process.
    • Close:  to close the wizard as it cannot perform an automatic update. You must manually update your team project as it has been customized beyond what the wizard can handle, or you created your team project using a process template that the wizard doesn’t recognize.

A successful update will return a success message.


If the wizard doesn’t succeed, you will receive an error message. It’s up to you at that point to manually resolve any errors and complete the update.  There’s more information on MSDN: Resolve Errors Received After an Automatic Update for guidance.

In most cases, congratulations, you’ve enabled features for your upgraded team project! However, in order for your developers to start using those features in Team Web Access, you’ll need to configure the default team for the upgraded project. You can find all those steps here. You’ll also need to understand what features are available for your users, and if necessary, configure access to features.

However, if you’re using the Agile process template, or you want access to add the shared queries feature to your team project, there’s a little more work to do. Fortunately, you can go read all about it and find the steps here.

There’s more information on MSDN: Update an Upgraded Team Project to Access New Features and Manual Updates to Make After Features are Enabled.

13 thoughts on “Run the Configure Features Wizard

  1. I tried to do this on my TFS 2012 RC, but when I click Verify in the ‘Configure Features’ popup dialog, I get ‘The following error occurred: Value cannot be null. Parameter name: stream’. Please advise.

  2. Hi, Leon. I’m going to forward your comment to someone on this feature team.

  3. Anon test

  4. Leon, could you look at the eventlog on the Application Tier and post the error message?

  5. Sure, first I get the text ‘Ispecting process templates for compatibility with your team project…’. A few seconds after that the exception. In the Event Viewer, I have this event from source ‘Windows Error Reporting’.
    Fault bucket , type 0
    Event Name: TeamFoundationUE
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 1.0.0.0
    P2: tfs
    P3: 11.0.50522.1
    P4: 11.0.0.0
    P5: General
    P6: ArgumentNullException
    P7: B651A6E5ADE95AE3
    P8: 831F7EFA
    P9:
    P10:

    Attached files:

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_1.0.0.0_cedf858670c564bd157d582af6465962ac9d2_0b5ffc73

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 49709b3b-ad70-11e1-9093-40402b93d67b
    Report Status: 4

    The WER file contained this:

    Version=1
    EventType=TeamFoundationUE
    EventTime=129831969588204475
    Consent=1
    ReportIdentifier=49709b3b-ad70-11e1-9093-40402b93d67b
    Response.type=4
    Sig[0].Name=P1
    Sig[0].Value=1.0.0.0
    Sig[1].Name=P2
    Sig[1].Value=tfs
    Sig[2].Name=P3
    Sig[2].Value=11.0.50522.1
    Sig[3].Name=P4
    Sig[3].Value=11.0.0.0
    Sig[4].Name=P5
    Sig[4].Value=General
    Sig[5].Name=P6
    Sig[5].Value=ArgumentNullException
    Sig[6].Name=P7
    Sig[6].Value=B651A6E5ADE95AE3
    Sig[7].Name=P8
    Sig[7].Value=831F7EFA
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.274.10
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    FriendlyEventName=TF30068: An exception has occurred in a Team Foundation component: Value cannot be null./r/nParameter name: stream
    ConsentKey=TeamFoundationUE
    AppName=tfs
    AppPath=C:\Windows\System32\inetsrv\w3wp.exe
    ReportDescription=TF30069: An unexpected condition has occurred.

  6. Hi Leon,

    There are couple things we can try to see if we can narrow down the problem.

    Does this issue repro, if you try to run feature enablement again?

    Let’s make sure the proccess template are uploaded properly to this collection. Can you try downloading all the process templates on the TPC using the process template manager.

    If you are familiar with debugging in Visual Studio, and you have VS on the same box as TFS server, you can try attaching to w3wp.exe just before you hit Verify and try to capture the stack trace with values if possible.

    Thanks.

  7. Hi,

    Yes I can repro this issue.
    I did some additional test. I got at least 2 projects upgraded, so sometimes it does work!

    I’m not using the DefaultCollection, but one I created later, back in the days of TFS 2010.
    I’m experiencing the ArgumentException-issue with all Projects in this TPC.
    I am using a Scrum template with 2 custom WITs, no SharePoint configured.

    I have another TPC, also from before the upgrade and I can successfully upgrade all projects in this TPC.

    Furhermore, I attached the VS 2012 RC debugger to the w3wp.exe app pool, but it didn’t catch our output the exception. Also not with IntelliTrace 😦

    I appreciate the help efforts.

  8. I was having the same issue with my deployment. Ironically when I attached remote debugger to troubleshoot the issue, it started working. Try that and see if it works for you.

  9. To be a little more specific since I realize that last post was a little vague.

    Use visual studio, either local or remote to debug the process w3wp.exe on the TFS application tier server.

  10. Tim, I was hoping you could help me out –
    When I run the Configure Features Wizard, I see this message:

    The following features have not been configured for this team project.
    •Code Review
    •My Work
    •Feedback
    •Planning Tools
    •Storyboarding
    Learn more about these features

    After I click on Verify, this message appears:
    ‘There are no process templates available with valid configuration settings for this team project.’
    I’ve downloaded the MSF for Agile Software Development 6.2, but I can’t figure out how to enable access to these features.

    Could you provide any guidance?

  11. Adrian, it sounds like the wizard can’t update the team project you’re trying to upgrade. You may have to do it manually. Here is a link that explains how:

    http://msdn.microsoft.com/en-us/library/ff432837.aspx#manual_updates

    Do you know what process template was used to create the team project you’re trying to update? I’m guessing you’re coming from TFS 2008 or earlier? Depending on the version of TFS you’re trying to install, a new process template (with all the features listed) will be used for all _new_ team projects. The template you downloaded (MSF for Agile Software Development 6.2) is the one included with TFS 2012.2. Now the latest template name is the same as the version number of TFS.

    All of the new one templates already have the features listed, and adding new features with each new release is done by way of running the wizard. But — getting the new agile features to work in older projects (TFS 2008/TFS 2005) is a manual job. Take a look at the page linked above. If you run into trouble, I’m happy to help.

    Good luck!

  12. Tim, thanks for your help. I was able to manually resolve this with the instructions in the link you provided, although it wasn’t as smooth as I would have liked.
    I appreciate you getting back to me.

  13. Good to hear! I’m sorry it wasn’t a smoother process. Hopefully it’s smooth sailing from here on out.

Leave a comment