none
Managed Metadata causes Word 2013 to crash

    Question

  • Hi,

    when I open a Word document (or create a new one) in a document library with a managed metadata column, Word or Excel starts to open but crashes directly. I removed all other columns and also changed managed metadata to include only text values to get sure it's no other Problem.

    Checked this also on another client and got same result. Can someone test this in a different environment?

    Office Enterprise 2013 32bit installed.

    Thanks & regards

    Nikolas

    Thursday, December 06, 2012 2:35 PM

Answers

  • I also had some Office 2010 products installed in parallel with Office 2013. And SharePoint Designer 2010. To be able to get Office 2013 (Word and PowerPoint) to edit Managed Metadata fields, I had to uninstall everything with Office 2010 and Designer 2010.

    I then made a Repair of Office 2013, restarted the computer and then it worked again!

    Hope this helps!

    Matz



    • Edited by Matz Höög Monday, April 22, 2013 9:52 AM
    • Proposed as answer by alxdean Wednesday, June 05, 2013 11:44 PM
    • Marked as answer by Nikolas Orelly Friday, June 14, 2013 9:15 AM
    Monday, April 22, 2013 9:51 AM

All replies

  • Hi Nikolas,

    I am unable to reproduce the problem you are having we use managed metadata columns all the time...

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.

    Saturday, December 29, 2012 2:38 PM
  • I've got exactly the same problem.

    Client: Windows 8 & Office 2013 RTM

    The problem happens on all SharePoint Platforms when a Managed Metadata Term is used from the Term Store. SharePoint 2010, SharePoint 2013 RTM and Office 365 (2010 & Preview).

    When opening the file at first, it works. Open the document information panel and Word crashes. So it actually is the DIP causing word to crash when a managed metadata column is used on the library.

    This happens on both columns added to the library directly and columns added to a content type.

    Also on a closely related issue, Skydrive Pro fails to synchronise the library if a MMS term is used.
    SkyDrive Pro Error details:

    We can't synchronize this tool because of an unknown error.

    or sometimes a bit more useful:

    RecordDatabase: Field "TaxKeyworddtdxcqknmd68tndzd7mner3j4rt47ax44hj9i6s" not found.
    Error code=0x80070057; Error source=Groove

    Very depressing indeed.

    Alex

    Wednesday, January 16, 2013 2:49 AM
  • Thanks for testing it. At least I know it's not (directly) related to our environment.

    Nikolas


    Wednesday, January 16, 2013 2:09 PM
  • We are experiencing this exact issue from all office 2013 apps.  Any content type with managed metadata causes the office app to crash.  This makes 2013 completely unusable !

    Thursday, January 17, 2013 6:44 PM
  • Hi All,

    Interesting can you upload a screenshots, error logs or any additional information to skydrive so I can download and check it out? I have several SharePoint 2013, 2010 with Office 2013 environments and I have not been able to duplicate the error. Also, is everyone seeing the same error in their event log as Alex?

    RecordDatabase: Field "TaxKeyworddtdxcqknmd68tndzd7mner3j4rt47ax44hj9i6s" not found.
    Error code=0x80070057; Error source=Groove

    Please upload any additional information that you think will be helpful as I would love to be able to reproduce so that we can resolve? I will upload a couple MP4s so you can check out my demo environments as time permits.. One last thing just to be in sync, there are Office Web Apps 2013 and Office Professional 2013. My assumption has been  we are discussing Office Professional 2013 installed on your desktop?

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    Thursday, January 24, 2013 12:14 AM
  • Hi Ivan,

    Screenshots are not too interesting, but i uploaded them to:

    https://skydrive.live.com/redir?resid=5499043D96079F4F!115&authkey=!AMH28SXyPJ3ujbA

    I created a new library and just added a single managed metadata column. Office Professional 2013 is installed on the Desktop.

    In event log I only got this:

    Faulting application name: WINWORD.EXE, version: 15.0.4454.1004, time stamp: 0x50bda088

    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82

    Exception code: 0xc0000374

    Fault offset: 0x000da94f

    Faulting process ID: 0x1b7c

    Faulting application start time: 0x01ce008ea7ccd736

    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE

    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Report ID: e6f48222-6c81-11e2-be83-d4bed91214f4

    Faulting package full name:

    Faulting package-relative application ID:

    Thanks
    Niko
    Friday, February 01, 2013 3:44 PM
  • Exactly the same error I get.

    Faulting application name: WINWORD.EXE, version: 15.0.4454.1004, time stamp: 0x50bda088
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
    Exception code: 0xc0000374
    Fault offset: 0x000da94f
    Faulting process id: 0x24a4
    Faulting application start time: 0x01ce0095f79e21fa
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\WINWORD.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 3ca60fb4-6c89-11e2-be89-a0b3ccfc398a
    Faulting package full name:
    Faulting package-relative application ID:

    Friday, February 01, 2013 4:09 PM
  • Hi

    Thanks for the screenshots...

    are you running any addins and do you have of the 2010 releases installed like Visio, Project etc..

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    Friday, February 01, 2013 4:16 PM
  • I have disabled all add-ins as a test, but no success.  And the only 2010 product installed is Microsoft Office Upload Center.

    I truly believe Microsoft did not test this product at all.  Outlook 2013 has so many bugs it is insane and none of the integration to SharePoint works properly.

    Crazy.

    Friday, February 01, 2013 4:21 PM
  • HI,

    the reason I asked about 2010 products installed is when the 2007 release and again with the 2010 release of office I had strange issues that I couldn't explain. Since I am often working with betas and need to keep a somewhat stable environment while I am in the field. I noticed anomalies that the only solution was to remove the older products.  Microsoft like all software companies uses the same naming conventions and keys for their assemblies and they do not overwrite the older ones if the app is left installed and not either upgraded or removed prior to the installation. This will cause issues that you probably have never seen before, Is there a way you can bring up a VM on perhaps a Windows 8 Desktop that only has Office 2013 installed to verify the problem still exists. in the meantime I will find the references to the documented errors we found due to having both version of Office installed. Though will most likely not be the same error you are having as they present themselves I numerous ways. One of the ones that I had was in receiving alerts for approval, I could preview the document in Outlook but not open it to click on approve. :Please let me know what you find and I will post the links to the articles later this weekend..

    -Ivan


    Ivan Sanders My LinkedIn Profile, My Blog, @iasanders, Business Intelligence in SharePoint 2013.

    Saturday, February 02, 2013 3:47 PM
  • Hi,

    might be the reason. I have Outlook 2010 and SharePoint Designer 2010 installed. Will try to set up a VM without any Office 2010 components and post the results.

    Thanks for looking into this.

    • Proposed as answer by Matz Höög Monday, April 22, 2013 9:48 AM
    Monday, February 04, 2013 7:22 AM
  • Yes,

    That is very possible. I had Visio 2007 and Project 2007 installed with Office 2010 and wasn't able to open Alerts. I had to read them using the treading pane in outlook. here are many stories folks many folks on having two version of Office products installed.

    Please let us know how it goes as we want to see your problems resolved...

    -Ivan


    Ivan Sanders My LinkedIn , My Blog, @iasanders, BI in SP2013, SP2013 Content Packs.

    Wednesday, February 06, 2013 10:19 AM
  • Ok,
    it really seems that this is the problem.  A new installed computer with Office 2013 didn't showed this behaviour. Even after Outlook 2010 was installed, DIP showed up and Office didn't crash on this machine.  

    Will try to figure out which Office 2010 component is causing problem...
    New Microsoft Updates (February Patchday) had no influence on the other machines.

    Nikolas

    Wednesday, February 13, 2013 3:57 PM
  • Some additional information:

    - reinstalled System Windows 8 64bit
    - installed Office 2013 Plus 32bit (without Outlook)
    - installed Outlook 2010 32bit

    DIP was ok when opening documents from SharePoint with Managed Metadata

    - installed SharePoint Designer 2010 32bit (Chose only the Designer component during Installation)

    DIP crashes when opening documents from SharePoint with Managed Metadata

    Thursday, February 21, 2013 8:09 AM
  • Hi Nikolas,

    That's interesting.

    InfoPath does NOT support Managed Metadata columns. ... and you can NOT add a Managed Metadata column with SharePoint Designer 2010. Also, Best Practice is to NOT mix Office Versions there are shared assemblies in the GAC that have been deprecated from version to version. You will have issues and they can be difficult to diagnose... If I may ask why are you installing Outlook 2010?

    -Ivan


    Ivan Sanders My LinkedIn , My Blog, @iasanders, BI in SP2013, SP2013 Content Packs.

    Friday, March 01, 2013 11:39 AM
  • Hi Ivan,

    yes, I would avoid to install several Office Versions but we still have an Exchange 2003 environment and until it is upgraded we cannot use Outlook 2013. But we don't have many users who need SharePoint Designer, so if it's working with the above configuration i'm fine. Will try it with some other maschines....

    At least we could figure out what components causes this behaviour.

    Thanks again for your help.
    Nikolas

    Monday, March 04, 2013 9:27 AM
  • I also had some Office 2010 products installed in parallel with Office 2013. And SharePoint Designer 2010. To be able to get Office 2013 (Word and PowerPoint) to edit Managed Metadata fields, I had to uninstall everything with Office 2010 and Designer 2010.

    I then made a Repair of Office 2013, restarted the computer and then it worked again!

    Hope this helps!

    Matz



    • Edited by Matz Höög Monday, April 22, 2013 9:52 AM
    • Proposed as answer by alxdean Wednesday, June 05, 2013 11:44 PM
    • Marked as answer by Nikolas Orelly Friday, June 14, 2013 9:15 AM
    Monday, April 22, 2013 9:51 AM
  • Thank you Matz for the hint,

    Found out that Office 2013 Repair solved the Problem even if Outlook 2010 and Designer is still installed.  I assume that the reregistration of the InfoPath components is doing the trick.

    Nikolas

    Friday, June 14, 2013 9:15 AM