locked
Problem with Update of Sharepoint Taxonomy Fields in custom developed Content Types RRS feed

  • Question

  • Dear all,
    
    we developed an solution on sharepoint 2010 for one of our customers with custom lists and content types
    with fields from the managed meta data store. As recommended we developed everything in features & solutions so that easy deployment is possible. Adding metadata to the termstore seems to work without problems, but today we stepped over an confusing issue: Our customer changed the default label of an term in the metadata term store, but the label did not change
    in listviews and detailviews of items in the specific sitecollection. In editview we see the correct label. After searching a while we discovered the connection between the sitecollection and the term store,
    the hidden Taxonomylist (/Lists/TaxonomyHiddenList/AllItems.aspx) in the sitecollection, which seems to map the terms. After testing we discovered that the term/label did also not change in the hidden taxonomy list.
    The Timerjob “Taxonomy Update Scheduler“ is running hourly with success and we also tried to start the job manually,
    but the label did not change in the hidden list. Also there are no errors in the logfiles in verbose mode. We also tested to create a managed metadata field manually, put it in a list and after that, changed the label.
    For whatever reason the update of labels on manually created fields works without a problem. Our lists, content types etc get created programmatically, the fields are created on sitecollection
    level and also the content types, after that the content type is applied to the list. Question: Is there an attribute which is important to include in the creation of the elements (in the feature),
    so that it is possible to update the labels of already created terms or is this an SP 2010 Known Issue?

    I would be very thankful to get a hint on that problems
    Wednesday, September 15, 2010 9:08 AM

All replies

  • Hello paxvas,

    I have exactly the same problem. The values aren't updated by the Taxonomy Update Scheduler in http://[rootsite]/lists/taxonomyhiddenlist

    Have you found a solution yet?


    turbodude
    • Proposed as answer by GOWNET Wednesday, March 7, 2012 8:00 AM
    Thursday, October 21, 2010 6:44 AM
  • Did you use the blank site template when creating your site collection? There is a bug in it (unfortunately I can't remember were I found this information), the permissions on the hidden taxonomy list are not set correctly. Please read this article: http://blogs.technet.com/b/seanearp/archive/2010/07/28/sharepoint-2010-403-error-when-updating-metadata.aspx. I'm not sure but maybe it has something to do with your issue.
    Thursday, October 21, 2010 3:53 PM
  • Do the GUIDs in the THL listitems and your list listitems match up?

     

    Here is a blogpost of mine that may (or may not) be of help.

    http://davidfrette.wordpress.com/2010/05/25/how-managed-metadata-is-stored-in-sharepoint-lists/


    SharePoint Solution Architect, Developer
    Thursday, October 21, 2010 5:26 PM
  • The taxonomy values in the list are matching the values in the TaxonomyHiddenList when viewing the items in the listview mode or when viewing the properites of the item.

    If I select edit properties, the correct value from the "Term Store Management Tool" ís shown.

    So the problem for me is that the job "Taxonomy Update Scheduler" (which runs in order to update the TaxonomyHiddenList) runs but doesn't update the values in the TaxonomyHiddenList.

    I have tried to add administrators to the "Manage Metadata Service" in "Manage Service Applications" in Central Admin. I have also tried to add a new application pool with no success.

    Any ideas?


    turbodude
    Friday, October 22, 2010 9:55 AM
  • Hi paxvas,

    Have you moved/backup/restore/test->prod content databases?
    This wil break the relationship between the Taxonomy Service and the Content Databases.

    Kind regards,
    Joran Markx


    Joran Markx DiVa BV (The Netherlands) Blog - http://blog.diva.nl Website - http://www.diva.nl
    Friday, October 22, 2010 10:14 AM
  • I found an interesting article about the Taxonomy Fields
    http://www.wictorwilen.se/Post/Dissecting-the-SharePoint-2010-Taxonomy-fields.aspx

    Kind regards,
    Joran Markx


    Joran Markx DiVa BV (The Netherlands) Blog - http://blog.diva.nl Website - http://www.diva.nl
    Friday, October 22, 2010 10:18 AM
  • I have not moved/backup/restore any database. We have the problem both in our development environment and the same problem exists on the customer's server.

    It's driving me crazy. I will use a ticket in our support agreement with Microsoft to find out what the problem is.


    turbodude
    Friday, October 22, 2010 11:58 AM
  • I don’t know how this problem has occurred but I suspect that when deleting a site collection the referring rows for the site collection id aren’t removed from the ECMUsedTerms table in the Managed Metadata Service database.

    It seems like the Taxonomy Update Scheduler Timer job loops through all rows in ECMUsedTerms and for each row it checks the SiteGuid against the existing site collection ids. If no Site collection exists for the guid an exception is thrown in SharePoint log and the job is terminated(!).

    Example of error description:

     


    turbodude
    Wednesday, October 27, 2010 9:13 AM
  • Sorry I couldn't post my whole answer.

    Here is the error description:

    “Exception occured while hidden list being updated: System.IO.FileNotFoundException: The site with the id 4e1543f0-cb60-49a0-a2c5-09139f504831 could not be found.     at Microsoft.SharePoint.SPSite..ctor(Guid id, SPFarm farm, SPUrlZone zone, SPUserToken userToken)     at Microsoft.SharePoint.SPSite..ctor(Guid id)     at Microsoft.SharePoint.Taxonomy.UpdateHiddenListJobDefinition.ProcessProxy(MetadataWebServiceApplicationProxy proxy)     at Microsoft.SharePoint.Taxonomy.UpdateHiddenListJobDefinition.Execute(Guid targetInstanceId)”


    turbodude
    Wednesday, October 27, 2010 9:14 AM
  •  And here is the solution: 

            Open the “Managed Metadata Service _GUID” database. And check which terms that are used for the site that doesn’t exist. Select to “Open Table/Edit rows”

    SELECT     PartitionId, WebAppId, ContentDatabaseId, SiteGuid, TermSetId, TermId
    FROM         ECMUsedTerms
    WHERE     SiteGuid = '4e1543f0-cb60-49a0-a2c5-09139f504831'

    Delete the rows. Check if there are more obsolete siteguids.

    SELECT DISTINCT UT.SiteGuid
    FROM ECMUsedTerms UT
    LEFT JOIN [SharePoint_Config]..[SiteMap] SM
    ON UT.SiteGuid = SM.ID
    WHERE SM.ID IS NULL

    Delete the rows for all obsolute siteguids. Then run the Taxonomy Update Scheduler and the TaxonomyHiddenList is updated.

    Be careful when deleting data in the source database. I found the solution by myself. Looking forward to the answer from Microsoft.


    turbodude
    Wednesday, October 27, 2010 9:19 AM
  • Your solution puts your database in an unsupported state.

    Support for changes to the databases that are used by Office server products and by Windows SharePoint Services
    http://support.microsoft.com/kb/841057

    If you still have backups from before your manual alteration you can proceed forward with a support incident if you are not already in the process.

    Please let us know the outcome of the support incident or if you have not opened one yet please feel free to visit the link below and see if any paid support option available may suit your needs:
    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone


    Fred Ellis - MSFT - "Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread."
    Wednesday, November 3, 2010 2:55 PM
  • I have the same problem too. After changing the Default label for a term the existing lists still displays the old label but editing the item shows the new label. Did Microsoft give you a supported solution? Please let me know since I would rather avoid editing the database directly.

    I have a Microsoft support incident open also BUT if you have a solution already it would help me fix this faster and save some aggravation.  Thanks.

    Monday, January 10, 2011 4:08 PM
  • The support issue at Microsoft is still open. I think it will last a couple of weeks before they will supply a solution.


    turbodude
    Tuesday, January 11, 2011 12:10 PM
  • Would be great if you could update here once you receive a response from MS - same issue for me on dev and production environments
    • Edited by Shaz Bux Tuesday, January 11, 2011 1:08 PM typo
    Tuesday, January 11, 2011 1:07 PM
  • Yes, looks like this one will take a while to investigate and I was told the fix may not be available till the service pack or future cumulative update is released. But, I will post updates here.
    Monday, January 17, 2011 7:05 PM
  • Thursday, March 3, 2011 2:27 PM
  • Thanks for the update. We had our users edit the lists manually and update the terms since we did not have an enormous number of items / lists to update. We had to move on since there was no ETA for the fix to be released.
    rcusa
    Thursday, March 3, 2011 10:04 PM
  • How did you find this workaround? I guess you follow this blog.
    rcusa
    Thursday, March 3, 2011 10:05 PM
  • We have a support issue at Microsoft regarding this problem and the guy who is responsible posted this in the blog. He told me that hopefully they will have a solution for the problem in the June CU.
    turbodude
    Thursday, March 3, 2011 10:13 PM
  • I also have a ticket open with Microsoft support but the Tech I am working with may not be aware or was busy. Thanks.
    rcusa
    Friday, March 4, 2011 1:55 PM
  • Thanks to turbodude providing the link here. It's hard to post information everywhere it might help so please apologize that I was not on this thread.

    @rcusa, I think I'm in contact with your MS contact because he asked for a hotfix number. We have currently no offial ETA for a possible fix but I'm sure we should have it in one of the next CU's.

    The workaround was an idea from the product group and it works perfect in my test environment. Some powershell code and voila also C# works inside PS.

    Friday, March 4, 2011 4:42 PM
  • Thanks Joerg, since we have already resolved the issue by manually editing the list items we don't need to apply the workaround and will wait for the fix.
    rcusa
    Monday, March 7, 2011 2:30 PM
  • Thanks for the update, I will download the June CU and review the list of hotfixes.

    I reviewed the SP1 list of issues and it had about 300 fixes. Now we begin testing SP1 and June CU in DEV!!!


    rcusa

    Wednesday, June 29, 2011 7:08 PM
  • Hi;

    We ran into a similiar issue.  

    I wrote a block as a work around to this problem.

    http://spcrew.com/blogs/Lists/Posts/Post.aspx?ID=13

    thanks

    Charles

    Friday, April 13, 2012 5:44 AM
  • https://msisgreat.net/2018/08/21/recursively-update-file-metadata-taxonomy-field/


    Regards Senthamil

    Tuesday, August 21, 2018 9:26 AM