locked
Confusing issue: Office 2007, .docx, MOSS 2007 - cannot modify metadata RRS feed

  • Question


  • Environment: 

    MOSS 2007 SP3 12.0.0.6608 running on Windows 2003 R2 Standard x64 SP2
    3 MOSS server: 1 Index server; 2 WebFrontends accessible through Windows NLB
    2 SQL Server 2005 backends in a cluster

    We are using several custom content types inheriting from the MOSS “document” content type. Those are using some default and some custom columns (most likely lookup fields) for metadata and each has got an Office 2007 template (Word). The templates (.dot) are using macro code to get information prefilled. This is on MOSS side handled by a custom event receiver. 

    Problem description:

    If you save a document created out of such a template as “docx” back to the document library you’ll experience that all custom metadata fields in MOSS are kind of “write protected”, you cannot change them. Every time you try to change it, the version number increases. If you change a default metadata field like “title” the changes are saved. If you afterwards change again one of the custom fields (which doesn’t work) the change to the title will be reverted to its initial entry. 
    This to me feels like it’s always going back to the V0.1 metadata when trying to change one of the custom fields.
    This occurs for all workstations.
    This all works if you save this document as a Word 2003 (doc) file, or when you just upload a document that hasn’t been created from a template (also for docx files). 

    The issue came up a few weeks ago, right before everything worked well. We already checked for updates that could have been applied at that date, but this wasn’t the case.


    Now it’s getting to the confusing part of the story:

    This all happens on “Farm A” like it’s described above. The farm is placed within one organizational unit in our domain. In there also the workstations/user objects are placed.
    Now we have also “Farm B” which has got the same architecture, but a slightly different configuration SharePoint wise and in regards to GPOs. The content types are basically configured the same way and the office templates are exactly the same.
    If you now go through the scenario described above using “Workstation B” on “Farm A”, everything works fine. If you do it vice versa, using “Workstation A” on “Farm B” also everything works perfectly well. (All visible in the picture below)

    The differences we have between the workstations are:
    Workstation A = Windows 7 x86, Office 2007 (including InfoPath)
    Workstation B = Windows XP x86, Office 2007 (including InfoPath)
    … and some GPOs  configured a different way. BUT: the fact that it all works using the machines of the other farm is really confusing. 

    What we’ve already done:

    • Already checked the template’s macro code if there is something suspicious
    • Made sure to have exactly the same (checked) templates available on both farms document libraries
    • Repaired the office installation on Workstation A because of possibly broken dll files regarding InfoPath and
    • possible issues regarding a n Office 2003 Product installed (i.e. Visio)
    • Also removed and reattached the Office Sharepoint Support Services within the office installation 
    • Followed these instructions: http://rhnatiuk.wordpress.com/2008/10/15/problem-showing-document-properties-in-word-2007 


    Thursday, October 25, 2012 8:26 PM

All replies

  • Hi,

    Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.

    Thanks,

    Entan Ming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contacttnmff@microsoft.com.


    Entan Ming

    TechNet Community Support

    Friday, October 26, 2012 10:08 AM
    Moderator
  • Hi,

    I think it would be best if you opened support ticket to look at why this is behaving this way on your farm.  From a high level it appears to be something client side with workstation A.


    Regards, Savoeurn Va Microsoft Online Community Support

    Wednesday, December 19, 2012 8:48 PM