Skip to main content

Microsoft Word 2010 crash while adding Quick Parts

MS Word 2010 was acting strange since a couple of weeks, it would crash the moment I add certain quick parts. I was editing a template for content type in SharePoint 2010 document library and it would crash Word. Clicking on the error details shows this:

Problem Event Name: APPCRASH
  Application Name: WINWORD.EXE
  Application Version: 14.0.7106.5001
  Application Timestamp: 520b3934
  Fault Module Name: wwlib.dll
  Fault Module Version: 14.0.7106.5001
  Fault Module Timestamp: 520b3985
  Exception Code: c0000005
  Exception Offset: 000107f6
  OS Version: 6.1.7601.2.1.0.256.48
  Locale ID: 2057

 Additional information about the problem:
  LCID: 1033
  skulcid: 1033

 Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

 If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I tried searching for a while but couldn't find any solution. This was happening to fields in the content type that are of type mult line textbox. I tried repairing Office but didn't help and then finally reinstalled Office and that seemed to fix the issue - well temporarily.

The same issue came up after a week and this time I didn't want to re-install Office. I noticed that Windows 7 applied some updates the previous day and there were some for Office as well. I did some more research and found similar issue discussed here:
Microsoft Forum  Thanks Ian!

That was the exact issue I was having, it seems the culprit was an update from Microsoft KB2760769 !! Uninstall this update and the issue was solved :)
Labels:

Comments

Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more