Sign in
 
HomeSharePoint Server 2010SharePoint Foundation 2010SharePoint OnlineLibraryForums
SharePoint Products > SharePoint 2010 Forums > SharePoint 2010 - Setup, Upgrade, Administration and Operation > Managed Metadata Service

Answered Managed Metadata Service

    •  
      Thursday, December 03, 2009 10:37 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi

      I have some problems configuring the Managed Metadata Service and help would be appreciated.

      I managed to add a new group into the Term Store Management Tool, with my own personal structure, not a problem here.
      But when I go to a document library or list and I want to make a new colomn of type Managed Metadata, then the problems begin. The notification       “The required feature is not enabled for this column type.” appears in the manage term set search box, but I cán search and find my defined taxonomy. When I try to OK this, following message (under this manage term set box) appears : “The Taxonomy feature (Feature ID "73EF14B1-13A9-416b-A9B5-ECECA2B0604C") has not been activated.”.

      I'm not able to find this specific feature and have every other feature necessary for the managed metadata options turned on.

      Anyone has an idea of what went wrong here?

      Joke

      • Moved by Mike Walsh FINMicrosoft Community Contributor Thursday, December 03, 2009 11:34 AM Clearly an Admin question. Please post to the most appropriate 2010 forum not to General unless it really is a General question (From:SharePoint 2010 - General Questions and Answers)
      •  
       

    Answers

    • Thursday, December 03, 2009 6:11 PM
      Owner
       
       Answered
      Sign In to Vote
      4
      Sign In to Vote
      You can use:

      stsadm -o activatefeature

         {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature ID>}

         [-url] <URL name>

         [-force]

      For example STSADM -o activatefeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -url http://<server> -force.

      Bill Baer, Technical Product Manager - US-SharePoint http://blogs.technet.com/wbaer
       

    All Replies

    • Thursday, December 03, 2009 12:12 PM
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote

      I managed to resolve it by activating the feature manually, using stsadm.

       
    • Thursday, December 03, 2009 12:15 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Please give the stsadm command you used. (So that people reading this thread later don't need to re-invent the wheel)

      (Either edit your above answer with the full command used (and re-mark as an answer) or post a new reply and mark that.)
      FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
      Complete Book Lists (incl. foreign language) on each site.
       
    • Thursday, December 03, 2009 6:11 PM
      Owner
       
       Answered
      Sign In to Vote
      4
      Sign In to Vote
      You can use:

      stsadm -o activatefeature

         {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature ID>}

         [-url] <URL name>

         [-force]

      For example STSADM -o activatefeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -url http://<server> -force.

      Bill Baer, Technical Product Manager - US-SharePoint http://blogs.technet.com/wbaer
       
    • Wednesday, February 24, 2010 5:06 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote
      I believe the following PowerShell command does the same:

      Enable-SPFeature -id "73EF14B1-13A9-416b-A9B5-ECECA2B0604C" -Url <Site-URL>


      Is that correct?

      Henrik
       
    • Monday, March 22, 2010 6:43 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      What is the name of the feature folder?
       
    • Monday, March 22, 2010 6:57 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote

      Found it: TaaxonomyFieldAdded

       
    • Tuesday, May 25, 2010 11:59 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I was having a similar issue (but I was trying to add an Enterprise Keywords column to a library in the root site of a site collection created using the blank site template). The "Enterprise metadata and keywords settings" option was not available under my library settings for a library in this site (alternatively a subsite using the blank template, or a site using any other template) had this option available under library settings.

      I used the powershell command as you have outlined above to activate the feature (appears to be a hidden feature so not available to active in the UI) and it worked for me.

       
    • Sunday, October 03, 2010 4:02 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Run from PowerShell: “Enable-SPFeature -Identity 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -Url <http://centaurus>"

      It runs fine ... but when I go to the site http://centaurus ... on the list, adding the new field of metadata managed still gives me the same error:
      NOT activated the feature taxonomy (ID feature "73EF14B1-13A9-416b-A9B5-ECECA2B0604C").
       
    • Friday, January 14, 2011 4:18 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Try activating the feature with ID 7201d6a4-a5d3-49a1-8c19-19c4bac6e668as well.
       
    • Friday, March 04, 2011 1:04 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote

      Hi All,

      hope this is the place to go... I have been facing this issue for a while now and cannot get the features to work.

      i have tried using both STSADM and PowerShell Comands on both Features;
      7201d6a4-a5d3-49a1-8c19-19c4bac6e668
      73ef14b1-13a9-416b-a9b5-ececa2b0604c

      all indicate that the commands succeded, however, going into the "      Document Library Settings / Change Column" still gives me the same

      The notification “The required feature is not enabled for this column type.” appears in the manage term set search box,

      following message (under this manage term set box) appears : “The Taxonomy feature (Feature ID "73EF14B1-13A9-416b-A9B5-ECECA2B0604C") has not been activated.”.

       I have tried disabling and both features and then re-enabling but no difference.

       

      Posted this into a new Question
      Enable Features - Managed Meta Data - MetaDataNav TaxonomyFieldAddedSubscribed

       
    • Thursday, April 07, 2011 10:14 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Hi,

      Maybe is the type of template that you are using to your site, try changing the site template to see if that solves the problem.

      Hope it helps.

       
    • Thursday, September 29, 2011 7:38 PM
       
        Has Code
      Sign In to Vote
      1
      Sign In to Vote
      If the site collection on which you are working was built on the "blank" template, you may also need to add the "Taxonomy feature stapler" feature as well. For some reason, Microsoft didn't include the ST#1 template as one of the ones that would get that feature applied by default. You can go in and add it to the XML so that it will add that feature by default to any new "blank" templates in the future (which is what I did for our farm). So in addition to stsadm -o activatefeature -name TaxonomyFieldAdded -url <site URL> also try adding stsadm -o activatefeature -name TaxonomyFeatureStapler -url <site URL> I like using the -name instead of the -Id because I am less likely to mistype a name than an Id code (I am somewhat dyslexic) Some sites also need stsadm -o activatefeature -name DocumentRouting -url <site URL> That one is if youo don't see the Content Organizer Settings and Content Organizer Rules (which would be part of a site using metadata to route files, like a RecordCenter or Doc Center). Hope that helps someone. Rebecca
       
    • Friday, September 30, 2011 3:09 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I had the same issue and was able to fixed it. You could refer

      http://sharepointconnoisseur.blogspot.com/2011/09/utilize-managed-metadata-service.html.

      Harry Chen