Word 2010 quick parts insert SharePoint label causes crash

I am using SharePoint Server 2010, with "labels" enabled in Content Types. When I open a Word document, I can see the label correctly (under Properties in File/Info). However, whenever I try to insert the label into the document as a field, using Insert/Quick Parts/Document Property, this causes Word 2010 to crash. Any ideas on how to fix this? It worked fine for me using SharePoint 2007 and Word 2007.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello Paul,

Thank you for posting your query in Microsoft Office Community.

Provide additional information for better assistance:

1) Does Word crash with any error?
Check and post back the error log from Event viewer to know more information reason for crash:
http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer

2) Does Word crash only while trying to insert SharePoint labels? If yes, you may also post this query in following TechNet forum for better suggestion:
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

Reply with necessary information and I’ll be glad to further assist you.

Thank You.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks Daniel. I found the following in the error log:

 

Log Name:      Application
Source:        Application Error
Date:          27/09/2013 14:29:54
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DOX-001-LTP1.doxeyforensics.local
Description:
Faulting application name: WINWORD.EXE, version: 14.0.7106.5001, time stamp: 0x520b38ed
Faulting module name: wwlib.dll, version: 14.0.7106.5001, time stamp: 0x520b390a
Exception code: 0xc0000005
Fault offset: 0x0000000000d8bda7
Faulting process id: 0x5ac
Faulting application start time: 0x01cebb85828814ef
Faulting application path: C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office14\wwlib.dll
Report Id: e43f4992-2778-11e3-948f-a460f5f4b786
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-27T13:29:54.000000000Z" />
    <EventRecordID>21526</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DOX-001-LTP1.doxeyforensics.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WINWORD.EXE</Data>
    <Data>14.0.7106.5001</Data>
    <Data>520b38ed</Data>
    <Data>wwlib.dll</Data>
    <Data>14.0.7106.5001</Data>
    <Data>520b390a</Data>
    <Data>c0000005</Data>
    <Data>0000000000d8bda7</Data>
    <Data>5ac</Data>
    <Data>01cebb85828814ef</Data>
    <Data>C:\Program Files\Microsoft Office\Office14\WINWORD.EXE</Data>
    <Data>C:\Program Files\Microsoft Office\Office14\wwlib.dll</Data>
    <Data>e43f4992-2778-11e3-948f-a460f5f4b786</Data>
  </EventData>
</Event>

 

Word has not crashed for any other reason so I will also post this to TechNet forum.

 

Paul

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Paul,

 

We have experienced the same issue:

 

Word 2010 32 Bit Crashes following inserting SharePoint 2007 Label via QuickParts

 

This issue was introduced by installing:

 

Security Update for Microsoft Word 2010 (KB2760769) 32-Bit Edition.

http://www.microsoft.com/en-au/download/details.aspx?id=40162

 

Simply uninstalling the Update resolved the issue for us.

 

It was reassuring to read your posts to realize that this was a general issue affecting multiple users and organizations.

 

I'll try to report this issue to Microsoft.

 

Ta, Ian Hearnes

 

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Happens every time with Office Word 2010 Win 7 x64.

I change the policy on the library and require a new label {Version }.

I Open a document and select to insert the new label in the head of the document.
It immediately crashes on selection 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, that is the problem I get. I have not tried to uninstall any updates, not least as I don't want to reintroduce any security vulnerabilities. Anyway, as mentioned by Jens I am running 64bit Word so the problem is not identical to Ian's.

 

I recently happened to spot that in SharePoint 2013 Microsoft has apparently removed the ability to insert labels into Word, so perhaps this functionality is no longer supported in SharePoint 2010?

 

I have not had much time to look into fixing the problem. However, I wonder if one possible work around might be to create a new field (column) in the SharePoint library to capture the version number. I suspect that would feed through correctly as a Word property. Obviously it would add time and risk to have to update the field manually. I've never used workflows but maybe one could design one to do that automatically on saving changes to documents?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

That helped, thanks Ian.

Regards,
Manoj

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Paul,

Thank you for posting your query in Microsoft Office Community.

Provide additional information for better assistance:

1) Does Word crash with any error?
Check and post back the error log from Event viewer to know more information reason for crash:
http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer

2) Does Word crash only while trying to insert SharePoint labels? If yes, you may also post this query in following TechNet forum for better suggestion:
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/threads

Reply with necessary information and I’ll be glad to further assist you.

Thank You.


Daniel - you've gone very quiet. Do you need any more information to enable you to assist me?

 

Paul

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Shurely that is just an ugly rumor... I know MS has removed a lot of basic stuff, like install projects, start menus...but there has to be some limit...
 
MS can not remove the main feature of having a tool integrated a document handling system.
Having document number and versions automated and printed is a sanitary issue for a document handling system such a sharepoint.

I have a situation where a company has gotten cold deployment feet because this feature is not working correctly. But I do have MSDN and I've started the process of being permitted to submit a request to ask for some professional support. If I get some answers (other than that I'm allowed to request a support I'll try to remember to post it here...)

Mean while I installed all the latest updates, but labels still fails on insertion.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

There is a list of discontinued features in SharePoint 2013 on the following Microsoft web page: http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/discontinued-features-and-modified-functionality-in-microsoft-sharepoint-2013-HA102892827.aspx 

 

It says:

 

"The ability to generate and embed a label containing metadata about a Word, Excel or PowerPoint document is no longer available. Settings for this feature have been removed." The reason given is:

 

"Feature does not meet compliance and records management user expectations"

 

I don't think the wording is very clear but I take it to mean metadata labels are discontinued in SP 2013. No further explanation is given and it may be that there something else to replace that functionality - e.g.  a different mechanism that does the same thing, such as inserting a document property rather than a label as such.  In SP2010 I have been able to insert number & single line text properties based on SharePoint columns.

 

Who knows? Let us know if you find out more!

 

 

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Oh dear... 

Well lets hope that they replace the somewhat awkward functionality rather than just removes it.
I would really like if I could add it as a standard document field such as version number, and as a document is added to a share point library that is replaced with a proper share point version policy.

All our trials on Server 2012, SQL server 2012, Win 8, VS 2012 failed, the improvements did not deliver and key functionality was removed without viable replacements. I left some running in production as they were neutral, but the migration work was a complete waste there was no gain.

Migrating customers to a new version of Office is not in the Cards for me...  
This is tricky because the Office 365 setup is really nice but the share point solution there must support office 2010, because I can't put my credibility on the line to replace an office suite that was really difficult to gain acceptance for to start with. 

I dread the idea of running Share point servers at different web hostels and dealing with a bunch of 3rd party suppliers.

MS keeps removing gnarly but functional solutions and replacing them with completely dysfunctional options. 
We'll see what MS reports back on this issue... Still if they remove a function surely they can't intend that Word should crash catastrophic, nor can they intend that all legacy processes will stop working.
I mean this is woven into the business fabric... you can't just remove it. 



Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated October 5, 2021 Views 2,543 Applies to: