1. The UI blocks this but does PowerShell or SharePoint Manager allow you to modify this? I get your point about the groups, I’m just offering a possible solution you may not have tried already.

  2. Hi, I’m not sure if you have fixed this, but it happened in my case, and I found the cause of it, I went to see the application logs and this is the error: Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type ‘Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker’ from assembly ‘Microsoft.SharePoint.Portal, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’.

    The solution is here: http://support.microsoft.com/kb/2481844

    Hope this helps

  3. Yes , that link he has given is working , &#44 replace with , in 14 hive Control templates\taxonomypicker.exe ‘s text first line. By Gajendra ,SharePoint Developer

  4. The managed metadata service is initialized in the Farm.
    The SP Groups are initialized in the Sites Collection.
    So, Managed metadata service can’t access to the SP Group at init.

    Use Active Directory Groups instead of Sharepoint Groups. It’s works fine ;)


Have a thought or opinion?