Word 2007 crashes when sving a document

Hey guys,
I have a user that is using Word 2007 on Windows XP sp3. When she tries to save a word document, Word crashes on her. It appears to do this randomly and there is nothing I can see that would trigger it. She can edit a document, save it
(using either quick save, or file, save) and it will crash on her. She's noticed more of a issue when she uses the quick save button. I have uninstalled Office twice. Once doing an uninstall/reinstall and the other doing an uninstall, delete the
directory and reinstalling word. The only add-on she has is Dorland's 28th edition dictionary. I have uninstalled/reinstalled this and the issue still seems to come up. I have gone through the registry and deleted any instance of Dorland's
I found. I did notice in the add/remove programs that there was a Dorland's lsited there, but could not be uninstalled. I am betting that could be the culprit. Anyone have any ideas?
Thanks,
David

See the KnowledgeBase article "How to troubleshoot problems that occur when you start or use Word 2010, Word 2007, Word 2003, or Word 2002" at:
http://support.microsoft.com/default.aspx/kb/921541?p=1
-- Hope this helps.
Doug Robbins - Word MVP,
dkr[atsymbol]mvps[dot]org
Posted via the Community Bridge
"whitehurstge" wrote in message news:[email protected]...
Hey guys,
I have a user that is using Word 2007 on Windows XP sp3. When she tries to save a word document, Word crashes on her. It appears to do this randomly and there is nothing I can see that would trigger it. She can edit a document, save it
(using either quick save, or file, save) and it will crash on her. She's noticed more of a issue when she uses the quick save button. I have uninstalled Office twice. Once doing an uninstall/reinstall and the other doing an uninstall, delete the
directory and reinstalling word. The only add-on she has is Dorland's 28th edition dictionary. I have uninstalled/reinstalled this and the issue still seems to come up. I have gone through the registry and deleted any instance of Dorland's
I found. I did notice in the add/remove programs that there was a Dorland's lsited there, but could not be uninstalled. I am betting that could be the culprit. Anyone have any ideas?
Thanks,
David
Doug Robbins - Word MVP dkr[atsymbol]mvps[dot]org

Similar Messages

Pages crashes when opening any document on iPad 3 Latest version. I could find on the net and finally deleted Pages from my device and reinstalled it. Still when I try to create anew document or open a document it just cr

Pages crashes when opening any document on iPad 3 Latest version. I tried everything I could find on the net and finally deleted Pages from my device and reinstalled it. Still when I try to create a new document or open a document it just crashes out.

Try this:
Make sure IOS is updated to latest version
Reboot device by pressing both the home button and sleep/wake (power) buttons at the same time for 10-15 seconds until the apple logo appears on the screen, then let go.
If that doesn't work then reset the device by going to settings/general/reset/reset all settings

InDesign cs3 crashes when opening CS2 documents

ID cs3 crashes when opening CS2 documents, not when open dialog appears, but after I choose file and it "starts" opening it. (core duo, xp, clean install, all updates)
If i open ID by opening file, it crashes with standard windows dialog, if I open ID first, it does not crash, but rather behaves strangely, nothing is opening, if I move a mouse it turns to sand clock.
Same thing happens on all machines with ID cs3 in my office.
All other apps works fine. I did read every single forum about ID crashing and nothing helps. Files resaved in interchange format opens well. There must be something in the files that ID cs2 did and what id cs3 cannot open :( Any ideas?

1. Is there any reason to use eps? Avoid it use AI, PSD or PDF instead.
2. Are all used fonts ok? What kind of fonts du you use?
3. Which Mac OS X do you use?
Does it crash with alwayst the same files?
What does the file history tell you? Hold down the command key and got to InDesign > About InDesign… Does it tell you somewhat more specific, like missing plugins, severly damaged files and restored files, when (in which version) the files have been created first (helps often to export to IDML and open this again and save it as INDD and work with the new file.), has the problematic file been converted from another application (Quark Xpress or PageMaker), etc.

Word 365 crashes when opening an attachment in Notes

Word 365 crashes when opening an attachment in Notes. I have tried a quick repair and an online repair. I have uninstalled Office 365 and reinstalled it. I have tried opening WINWORD in safe mode.

So the attachment itself is OK, and Word can open it successfully on the desktop. In this case, issue tends to be more on the Lotus Notes side.
We don't have a test environment for this currently, I'd suggest you check the Lotus Notes forum and see if other customers are having similar issues and any solutions out there.
On the Word side, you can check the event logs to see if there is anything useful there.
Regards,
Ethan Hua
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Word keeps crashing when I attempt to open an .docx email attachment, how do I fix this?

Word keeps crashing when I attempt to open an .docx email attachment, how to I stop word from crashing and be able to open the file?

Since Word is a Microsoft product, you might have better luck of getting an answer over on the Microsoft forum.

Word 2007 crashes during autosave and when saving as .DOC

Hi,
I have a problem with Microsoft Word 2007. It crashes every time during autosave. It also crashes when I try to save a file as .DOC (even an empty new file). When I save it as any other file type it's fine.
I have already tried repairing the office installation, reinstalling the whole suite (and then installing SP3 and all latest patches again), auto fix it from
http://support.microsoft.com/kb/822005/en-us and
http://support.microsoft.com/kb/921541/en-us, changing the autosave file location, using different windows account. None of these helped. I wouldn't like to work with autosave switched off.
I am using Windows 7 Professional SP1 and Office 2007 Professional 12.0.6683.5002 with SP3 on HP EliteBook 8470w.
-- Igor M.

Hi,
I tried to start Word in safe mode be it did not change anything. I also tried to start Windows 7 in clean boot but it did not help either (same issues).
Two entries are added to the event log when Word crashes:
First one:
ID: 0, Application Name: Microsoft Office Word, Application Version: 12.0.6683.5002, Microsoft Office Version: 12.0.6612.1000. This session lasted 94 seconds with 0 seconds of active time. This session ended with a crash.
Second one (Google translation):
Log Name : Application
Source: Application Error
Date: 2013-12-29 0:38:43
Event ID : 1000
Task Category : (100)
Level: Errors
Keywords: Classic
User : Not applicable
Computer: XXX
Description:
Name of the application causing the error: WINWORD.EXE , version : 12.0.6683.5002 , time stamp : 0x520bb457
Name of the module causing the error : wwlib.dll , version : 12.0.6683.5002 , time stamp : 0x520bb54c
Exception code : 0xc0000005
Fault offset : 0x0006d564
The process ID causing the error : 0xbb0
Time to run the application causing the error: 0x01cf0425b9f67b73
The application path causing the error: C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ WINWORD.EXE
The path of the module causing the error : C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll
Report ID : 2fcdf5c7 - 7019 - 11e3 - 96f9 - 1c3e84fe29b2
Event Xml :
  "><Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    "><Provider Name="Application Error" />
    1000</EventID>"><EventID Qualifiers="0"> 1000 < / EventID >
    100</Task>"><Task> 100 < / Task >
    "><TimeCreated SystemTime="2013-12-28T23:38:43.000000000Z" />
    Application</Channel>"><channel> Application < / Channel >
    "><Security />
  "><EventData>
    12.0.6683.5002</Data>"><Data> 12.0.6683.5002 < / Data>
    wwlib.dll</Data>"><Data> Wwlib.dll < / date >
    520bb54c</Data>"><Data> 520bb54c < / date >
    0006d564</Data>"><Data> 0006d564 < / Data>
    01cf0425b9f67b73</Data>"><Data> 01cf0425b9f67b73 < / date >
    C:\Program
Files (x86)\Microsoft Office\Office12\wwlib.dll</Data>"><Date> C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll < / date >
  ">< / EventData >
<span title="">< / Event >
Kind regards,

Acrobat pdfmaker com addin for word 2010 crashes when processing large files

I am trying to use the pdfmaker com addin for word 2010 to create a PDF document. Whenever I try and create the document, the acrobat addin crashes word.
I attempted to perform this on both an x86 and x64 machine and it failed both times at around the approximately same point (during/immediately after determining the bookmarks).
The document is large (862 pages, 2425 bookmarks, 311 300dpi graphics, for a total file size of 49.2MiB)
I can generate the PDF by just printing, but the whole point of using the pdfmaker is so that we don't have to perform 2.5K of manual cross-links.
Machine information:
Windows 7 (x64) SP1
Office 2010 (x64) 14.0.6112.5000
Acrobat X Pro (x86) 10.1.3
Crash Report:
Version=1
EventType=APPCRASH
EventTime=129853934132967189
ReportType=2
Consent=1
UploadTime=129853934134215189
ReportIdentifier=4e4f5b16-c16a-11e1-ae3f-5c260a5c33cf
IntegratorReportIdentifier=4e4f5b15-c16a-11e1-ae3f-5c260a5c33cf
Response.BucketId=41559749
Response.BucketTable=4
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WINWORD.EXE
Sig[1].Name=Application Version
Sig[1].Value=14.0.6024.1000
Sig[2].Name=Application Timestamp
Sig[2].Value=4d83e2f6
Sig[3].Name=Fault Module Name
Sig[3].Value=wwlib.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=14.0.6024.1000
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4d83e39e
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000031b4aa
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
UI[3]=Microsoft Word has stopped working
UI[4]=Windows can check online for a solution to the problem and try to recover your information and restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161 _none_08e61857a83bc251\MSVCR90.dll
LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df _5.82.7601.17514_none_a4d6a923711520a9\Comctl32.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\system32\nvinitx.dll
LoadedModule[17]=C:\Program Files\NVIDIA Corporation\CoProcManager\_etoured.dll
LoadedModule[18]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrapx.dll
LoadedModule[19]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[20]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[21]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\system32\ole32.dll
LoadedModule[23]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[24]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvdxgiwrapx.dll
LoadedModule[25]=C:\Program Files\Microsoft Office\Office14\wwlib.dll
LoadedModule[26]=C:\Program Files\Microsoft Office\Office14\gfx.dll
LoadedModule[27]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[28]=C:\Windows\system32\MSIMG32.dll
LoadedModule[29]=C:\Program Files\Microsoft Office\Office14\oart.dll
LoadedModule[30]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
LoadedModule[31]=C:\Windows\system32\msi.dll
LoadedModule[32]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[33]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[34]=C:\Program Files\Common Files\Microsoft Shared\office14\Cultures\office.odf
LoadedModule[35]=C:\Windows\system32\VERSION.DLL
LoadedModule[36]=C:\Windows\system32\uxtheme.dll
LoadedModule[37]=C:\Windows\system32\dwmapi.dll
LoadedModule[38]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[39]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[40]=C:\Program Files\Microsoft Office\Office14\1033\wwintl.dll
LoadedModule[41]=C:\Program Files\Common Files\Microsoft Shared\office14\1033\MSOINTL.DLL
LoadedModule[42]=C:\Program Files\Common Files\Microsoft Shared\office14\MSORES.DLL
LoadedModule[43]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSPTLS.DLL
LoadedModule[44]=C:\Program Files\Common Files\Microsoft Shared\office14\riched20.dll
LoadedModule[45]=C:\Windows\system32\mscoree.dll
LoadedModule[46]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[47]=C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL
LoadedModule[48]=C:\Windows\system32\Winspool.DRV
LoadedModule[49]=C:\Windows\system32\SHELL32.DLL
LoadedModule[50]=C:\Windows\system32\propsys.dll
LoadedModule[51]=C:\Windows\system32\ntmarta.dll
LoadedModule[52]=C:\Windows\system32\WLDAP32.dll
LoadedModule[53]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[54]=C:\Windows\system32\rsaenh.dll
LoadedModule[55]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[56]=C:\Windows\System32\msxml6.dll
LoadedModule[57]=C:\Windows\system32\profapi.dll
LoadedModule[58]=C:\Windows\system32\SXS.DLL
LoadedModule[59]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[60]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_88e41e092fab0294\MSVCR80.dll
LoadedModule[61]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\f73f0a9c9a83dcd3f f428be509a7992f\mscorlib.ni.dll
LoadedModule[62]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
LoadedModule[63]=C:\Windows\system32\WINTRUST.dll
LoadedModule[64]=C:\Windows\system32\CRYPT32.dll
LoadedModule[65]=C:\Windows\system32\MSASN1.dll
LoadedModule[66]=C:\Windows\system32\imagehlp.dll
LoadedModule[67]=C:\Windows\system32\ncrypt.dll
LoadedModule[68]=C:\Windows\system32\bcrypt.dll
LoadedModule[69]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[70]=C:\Windows\system32\USERENV.dll
LoadedModule[71]=C:\Windows\system32\GPAPI.dll
LoadedModule[72]=C:\Windows\system32\cryptnet.dll
LoadedModule[73]=C:\Windows\system32\SensApi.dll
LoadedModule[74]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Word.MathExtension.dll
LoadedModule[75]=C:\Windows\assembly\GAC\Extensibility\7.0.3300.0__b03f5f7f11d50a3a\Extens ibility.dll
LoadedModule[76]=C:\Windows\assembly\GAC_MSIL\office\14.0.0.0__71e9bce111e9429c\office.dll
LoadedModule[77]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[78]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Mathematics.Common.dll
LoadedModule[79]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\c40ec0f4cd203c88029 8f94c0427dd54\System.ni.dll
LoadedModule[80]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\222eb8aa336 953a6b0216db2b0c4770d\System.Drawing.ni.dll
LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\dc5bb 74eefdbf954cdfb70dd534d5564\System.Windows.Forms.ni.dll
LoadedModule[82]=C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\14.0.0.0__71e9 bce111e9429c\Microsoft.Office.Interop.Word.dll
LoadedModule[83]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\193d0 3ca60573c92f92d9b07fa5bc243\System.Configuration.ni.dll
LoadedModule[84]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\24d1b7ccbedaa36 02bae6a6acea9929e\System.Xml.ni.dll
LoadedModule[85]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathControls.dll
LoadedModule[86]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathEngine.dll
LoadedModule[87]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\sqmapi.dll
LoadedModule[88]=C:\Windows\system32\shfolder.dll
LoadedModule[89]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\MathRichEditNative.Dll
LoadedModule[90]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\mathenginen.dll
LoadedModule[91]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathResources.dll
LoadedModule[92]=c:\Program Files\Common Files\Microsoft Shared\VSTO\vstoee.dll
LoadedModule[93]=C:\Windows\system32\urlmon.dll
LoadedModule[94]=C:\Windows\system32\iertutil.dll
LoadedModule[95]=C:\Windows\system32\WININET.dll
LoadedModule[96]=C:\Windows\system32\Normaliz.dll
LoadedModule[97]=c:\Program Files\Common Files\Microsoft Shared\VSTO\10.0\VSTOLoader.dll
LoadedModule[98]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
LoadedModule[99]=C:\Windows\system32\oledlg.dll
LoadedModule[100]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[101]=C:\Windows\system32\MSVCR110_CLR0400.dll
LoadedModule[102]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\ec4aeb1a93320223 07604cba8284778b\mscorlib.ni.dll
LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\52974bd8d9753cf71a 27181621dcf4eb\System.ni.dll
LoadedModule[104]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\a4252f50e54a5 d2987e41709da9a117a\System.Core.ni.dll
LoadedModule[105]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V28a60cc2#\f165 482199ea49be235ec53ad93e6889\Microsoft.VisualStudio.Tools.Office.Runtime.ni.dll
LoadedModule[106]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O5949707a#\6d99 2851fc846eac2e388d2348711376\Microsoft.Office.Tools.ni.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V883708cb#\bc02 fe4c18b7e176e9bee4c72ff4cb32\Microsoft.VisualStudio.Tools.Applications.Runtime.ni.dll
LoadedModule[108]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V1955d7fd#\cc04 39da7e5347e89d6586ce262c1f69\Microsoft.VisualStudio.Tools.Applications.ServerDocument.ni.d ll
LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Vf9a08577#\86f6 f20538156d2008fff97542e09765\Microsoft.VisualStudio.Tools.Applications.Hosting.ni.dll
LoadedModule[110]=C:\Windows\system32\Secur32.dll
LoadedModule[111]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1204d7ae7e 0e637669e244a02b97983b\System.Drawing.ni.dll
LoadedModule[113]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\d7d8 56d242ddc80d696aa425195e5252\System.Windows.Forms.ni.dll
LoadedModule[114]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Deployment\475303e 370c565f47cd7d159485f24d9\System.Deployment.ni.dll
LoadedModule[116]=C:\Windows\system32\dfshim.dll
LoadedModule[117]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\0523 c17527d811bdc9606a0c62145f3d\System.Configuration.ni.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\771d4e20776373 ee95d2058b4d3f20a8\System.Xml.ni.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Security\819aca5f3 26d35ce5f478c20366d0f5c\System.Security.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\76b84571f 4497227f40c72e246939ac0\System.Xml.Linq.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oab3f8ec6#\0a3a f5db2975c482e98e96c99bb938af\Microsoft.Office.Tools.Word.Implementation.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O4a946565#\a550 db8b700051717681470a0b2b07d3\Microsoft.Office.Tools.Common.Implementation.ni.dll
LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O854200f9#\a3df 0bec1a202ce176b839f788d40f44\Microsoft.Office.Tools.Common.ni.dll
LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oeab01fba#\9d47 6070258253869ff6ca2201f33b54\Microsoft.Office.Tools.Word.ni.dll
LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O2eb0cc9a#\3994 dd35eb969eb2221f1886598f08cc\Microsoft.Office.Tools.v4.0.Framework.ni.dll
LoadedModule[126]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\2fd1 b7b3\d265be4b_e524cd01\PCREFindAddIn.DLL
LoadedModule[127]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\21e1 fe8e\00b3e430_67b7cb01\Microsoft.Office.Tools.Common.v4.0.Utilities.DLL
LoadedModule[128]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[129]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMOfficeAddin.dll
LoadedModule[130]=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
LoadedModule[131]=C:\Windows\system32\MSVCR100.dll
LoadedModule[132]=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
LoadedModule[133]=C:\Windows\system32\MSVCR110.dll
LoadedModule[134]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\USP10.DLL
LoadedModule[135]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
LoadedModule[136]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\1033\VBE7INTL.DLL
LoadedModule[137]=C:\Windows\assembly\NativeImages_v2.0.50727_64\stdole\be0906e176cf1f8ed8 1084df7042ee1c\stdole.ni.dll
LoadedModule[138]=C:\Windows\system32\explorerframe.dll
LoadedModule[139]=C:\Windows\system32\DUser.dll
LoadedModule[140]=C:\Windows\system32\DUI70.dll
LoadedModule[141]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7 601.17825_none_2b253c8271ec7765\GdiPlus.dll
LoadedModule[142]=C:\Program Files\Microsoft Office\Office14\msproof7.dll
LoadedModule[143]=C:\Program Files\Microsoft Office\Office14\MSOHEV.DLL
LoadedModule[144]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\1033\MSGR3EN.DLL
LoadedModule[145]=C:\Windows\system32\MPR.dll
LoadedModule[146]=C:\Windows\System32\drprov.dll
LoadedModule[147]=C:\Windows\System32\WINSTA.dll
LoadedModule[148]=C:\Windows\System32\ntlanman.dll
LoadedModule[149]=C:\Windows\System32\davclnt.dll
LoadedModule[150]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[151]=C:\Windows\system32\wkscli.dll
LoadedModule[152]=C:\Windows\system32\cscapi.dll
LoadedModule[153]=C:\Windows\system32\netutils.dll
LoadedModule[154]=C:\Windows\system32\SFC.DLL
LoadedModule[155]=C:\Windows\system32\sfc_os.DLL
LoadedModule[156]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Csi.dll
LoadedModule[157]=C:\Windows\system32\WINHTTP.dll
LoadedModule[158]=C:\Windows\system32\webio.dll
LoadedModule[159]=C:\Windows\system32\PSAPI.DLL
LoadedModule[160]=C:\Windows\system32\WS2_32.dll
LoadedModule[161]=C:\Windows\system32\NSI.dll
LoadedModule[162]=C:\Windows\System32\netprofm.dll
LoadedModule[163]=C:\Windows\System32\nlaapi.dll
LoadedModule[164]=C:\Windows\system32\srvcli.dll
LoadedModule[165]=C:\Windows\System32\npmproxy.dll
LoadedModule[166]=C:\Windows\system32\HLINK.DLL
LoadedModule[167]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[168]=C:\Windows\system32\WINMM.dll
LoadedModule[169]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\MSSP7EN.DLL
LoadedModule[170]=C:\Program Files\Microsoft Office\Office14\mscss7en.dll
LoadedModule[171]=C:\Program Files\Microsoft Office\Office14\css7Data0009.dll
LoadedModule[172]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMWord.dll
LoadedModule[173]=C:\PROGRA~2\Adobe\ACROBA~1.0\PDFMaker\Common\X64\ADOBEP~1.DLL
LoadedModule[174]=C:\Windows\system32\COMDLG32.dll
LoadedModule[175]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[176]=C:\Windows\system32\apphelp.dll
LoadedModule[177]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[178]=C:\Windows\system32\EhStorShell.dll
LoadedModule[179]=C:\Program Files (x86)\Google\Drive\googledrivesync64.dll
LoadedModule[180]=C:\PROGRA~1\MICROS~1\Office14\GROOVEEX.DLL
LoadedModule[181]=C:\Windows\WinSxS\amd64_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.61 61_none_0a1fd3a3a768b895\ATL90.DLL
LoadedModule[182]=C:\PROGRA~1\MICROS~1\Office14\1033\GrooveIntlResource.dll
LoadedModule[183]=C:\Windows\System32\cscui.dll
LoadedModule[184]=C:\Windows\System32\CSCDLL.dll
LoadedModule[185]=C:\Windows\system32\ntshrui.dll
LoadedModule[186]=C:\Windows\system32\slc.dll
LoadedModule[187]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[188]=C:\Windows\system32\actxprxy.dll
LoadedModule[189]=C:\Program Files\Internet Explorer\ieproxy.dll
LoadedModule[190]=C:\Windows\system32\thumbcache.dll
LoadedModule[191]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[192]=C:\Windows\system32\ieframe.DLL
LoadedModule[193]=C:\Windows\system32\OLEACC.dll
LoadedModule[194]=C:\Windows\system32\SearchFolder.dll
LoadedModule[195]=C:\Windows\System32\cscobj.dll
LoadedModule[196]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ACE.DLL
LoadedModule[197]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AGM.DLL
LoadedModule[198]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIB.DLL
LoadedModule[199]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIBUtils.DLL
LoadedModule[200]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\Cooltype.DLL
LoadedModule[201]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\JP2KLib.DLL
LoadedModule[202]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ARE.DLL
LoadedModule[203]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobePDFL.dll
LoadedModule[204]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobeXMP.dll
LoadedModule[205]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AXE8SharedExpat.dll
LoadedModule[206]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMEngine.dll
LoadedModule[207]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\pdfsettings.dll
LoadedModule[208]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\MPS.dll
LoadedModule[209]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFPort.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=41559749/nBucketTable=4/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Word
AppPath=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE

I recently ran into this with a bitmap in a 265 page document. I copied the bitmap to IrfanView and then back (I think that was the step -- I am already forgetting) and the copied it back. The problem went away. My student may look a bit more at the file -- I asked so I could give a more definitive comment here.
The result I had suggests that it is a problem in WORD or the bitmap that WORD was using. Why WORD can deal with it and not Acrobat, I am not sure. However, when printing to the Adobe PDF printer there was not a problem, just with PDF Maker.

Word 2007 Crashes

Every time I open Word 2007 it crashes. It also crashes while working in a document. Any help you can provider would be greatly appreciated. It is getting very frustrating. The following is the error message pops up:
Word has stopped working .....
Here are the crash details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 12.0.6690.5000
Application Timestamp: 52881869
Fault Module Name: gdiplus.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 515ba857
Exception Code: c0000005
Exception Offset: 737e74b2
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Brand: Office12Crash
skulcid: 1033
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Hi,
You can also try starting Word in Safe Mode:
Press Win + R and type “Winword.exe /safe” in the blank box, then press Enter.
If there’s no problem in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
In addition, I have seen such Word crash issues caused by conflicted programs, you can perform a clean boot to determine if background programs are interfering with Word:
http://support.microsoft.com/kb/929135
I hope this helps.
Regards,
Melon Chen
TechNet Community Support

Word 2007 doesn't open any documents.

Hello.
Our team are running Outlook 2010 and all the other office apps in 2007.
However, Word 2007 always has a problem with opening documents.
It works, shows none of error messages and the Word 2007 window opens properly but just doesn't show any documents.
To open a document, I have to drag and drop a document in Word 2007 that I want to.
After this small bothering task, everything works really fine.
I have changed every settings and add-in that could cause this issue.
To solve this problem Word 2007 has to be removed and installed again.
I'm really struggling to fix this issue but haven't found any reason.
Please help me with this issue!

Yes I thought of the same thing.
What I found was 2010 changed something in 2007 after Windwos Update.
This might be registries.
An error message box pops up saying 2007 got damaged when I try to remove 2007 from Programs and Features and the list of 2007 is just gone leaving all the functions and feature stayed on a computer.
Office 2007 still works after removing just 'the Office 2007 list' though.
In this case 2007 has to be installed(actually over-installed) AGAIN to write 2007's registry properly, remove 2007 than install 2007 again.
So annoying... to fix this issue, have to do this task...
As you mentioned, I need something to manage the registry and will read the description on the web page carefully.
Thank you so much. Stefan Blom.

Word 2007: Error when saving file that contains equations

Using Microsoft Word 2007, version 12.0.6425.1000 with Service Pack 2
I am a High School Math teacher, and when working on a document that contains a number of math equations. When I try to save the document, Word refuses to save. It displays the following error: "A file error has occurred. <filename>. OK",
and I am unable to save the file.
Reading the forum, I have found this to be a very common issue going back to 2009, but I have not seen a definitive solution or patch.
I have found a workaround:
Creat a new document
Copy and paste from the corrupted doc each page, saving the new document after each page
Until I hit the error, then I know the page that has the issue, and can usually narrow it down to a specific math equation. Nothing fancy just some basic math.
Manually rewrite the equation in the new document and it will successfully save.
But the issue has been occurring more and more frequently now and it is becoming very frustrating. Any help would be greatly appreciated!

There has been a long time known issue with the equation editor. it causes document corruption by "losing" XML tags.
Apparently fixes for some causes of these problems have been rolled out in Windows updates. But the problem still exists. You've got it easy. A lot of people running into this problem are students working on documents, like a thesis, that is on a short
deadline ...
One identified cause of these problems is editing equations
after you created them. DON'T DO THAT!
If you have to change an existing equation, create a new correct one and delete the old one.
Simpler fix. Don't use Word (or Office) for creating equations. Find some other product, like a pencil.
Over in the "Answers" forum there are a couple volunteers, Tony Jollans and Jeeped
, who have been manually fixing this type of error if you post a new question or add a reply to one of the ongoing discussions on this issue.
Sorry.
If you want to invest the time to figure out what your error looks like you may be able to come up with a fix other than copy /paste method.
Can't open Word File because of end tag/start tag mismatch error... XML Tag
- XML Error – Fix It tool - “The name in the end tag of the element must match the element type in the start tag”
This error is caused when Word either “forgets” to write an XML tag, or writes them in the wrong order.
Tony Jolans was the first person that I heard of with home made tool to fix the problem. Now MS has released a Fix It for one specific variation of the problem.
If the tools don’t fix your problem, the file will have to be fixed manually, repairing the tag order.
The Fix It article notes that the document is still in a fragile state. You have to do some addition fixing to avoid repeats of the problem.
https://blogs.technet.com/b/wordonenotesupport/archive/2011/03/24/error-when-opening-a-word-2007-or-2010-document.aspx
http://support.microsoft.com/kb/2528942- FIX IT
This fix it will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied.
Preventative suggestions
<snip Jeeped>
I don't think that anyone can completely stop editing equations, but pre-planning them should avoid unnecessary edits.
While I have no concrete, reproducible evidence that editing equations is a cause, I have made these empirical observations:
I cannot state precisely what many of the DOCX XML tags do, but basic XML syntax rules would suggest that code like:   <m:oMath><m:e><m:ctrlPr/></m:e></m:oMath>
... does nothing at all since it closes everything it opens and offers no content. It looks to me that this is a result of deleting one or more characters from an equation.
While Word 2010 reports these as a problem at: Line: 2 Column: 0 ... Word 2007 will still report the actual position, e.g.:
Line: 2 Column: 2726981 I keep a copy of Word 2007 side-by-side Word 2010 for no other purpose. It's the only Office 2007 program on my computer. This seems like it is actually a step backwards from a resolution since Word 2010 no longer seems
to be able to parse its own error.
Whether the syntax is truly useless and non-effective for any intent or purpose is actually beside the point. The syntax passes conformity tests and the DOCX
should launch. Why an 85 page document is 'broken' due to a few empty XML formatting tags while retaining legal syntax structure is beyond me.
I try to pass along the area that the problem was in and several times people have remarked that the area I report was the place they were last making modifications/deletions to equations (not additions) when the no-load corruption
occurred.
When no indication from the OP is offered on what was worked on last, the Line: 2 Column: 0 corruption often comes within a formula at the very end of the unfinished Word/Document.xml file and it may be inferred
that this was the last place being worked upon.
The corrupt DOCX files I've worked on are very commonly at the last stages of development with a large complex document. While there couldn't be a worse time for a corruption to appear, it would seem that small edits to existing content are causing
it and not large scale new content generation.
Not one of these points is a definitive 'smoking gun', but put together they seem to indicate
formula editing and not formula writing as a cause for the Line: 2 Column: 0 corruption. If it looks like a duck and quacks like a duck, it is most often a duck.
</snip>
Copy “True Autosave Macros for Office” to this place in reply
Let me fix it myself
If you are familiar with editing XML, you can try to fix the problem yourself by correcting the sequence of the mismatched oMath tags in the document. See the following example:
Incorrect tags:
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
<m:oMath>
</mc:AlternateContent>
</m:oMath>
Correct tags:
<m:oMath>
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
</mc:AlternateContent>
</m:oMath>
Note: You will have to use an application such as Notepad to edit the XML.
Manual Technique
<snip> A DOCX document is actually a .ZIP file that contains many internal components. There is an internal folder called word which will always contain a document.xml file. This file is the basis of the document's layout
and content.
Assuming that the DOCX archive structure has not been corrupted, it can be opened in an archive utility. I use
WinRAR for this. Once opened in
WinRAR, you can drill down into the
word folder and see the document.xml file. I use
Notepad++ as a text editing tool and have the .xml file extension associated with this program so i can simply double-click
document.xml in WinRAR to open an editing session.
Notepad++ has cursor positioning in the right-hand side of the status bar and finding the position of the error (supplied by a failed open in Word) is pretty straightforward. I look for empty formatting
tags first and only remove content if removing empty tags does not allow the document to be opened. I try to note existing content in the area that I make modifications in order that I can supply position reference information to the owner of the DOCX.
When editing, I assume the philosophy that kess is more. My target is to get the document to open in Word with as little modification as possible and let the original owner of the DOCX make any necessary adjustments.
I should mention that after making a change to word/document.xml you need to save it in
Notepad++ then go to
WinRAR and acknowledge that you want to update the file in the DOCX archive. Once the archive is updated, you can attempt to open the DOCX in Word to see if your efforts are successful.
WinRAR
Notepad++
</snip>
Further Fixes
The Fix it solution in this article should let you recover your Word document. However, the symptoms will reappear when you make any further edits to the document unless the core problem in the structure of the document is resolved.
To try to correct the core problem, follow one of these workarounds:
Install Office 2010 Service Pack 1
Office 2010 Service Pack 1 resolves this issue for new files. It will also prevent the problem from recurring with any files that were recovered with the Fix it solution in this article.
To download Office 2010 Service Pack 1, follow the steps provided in this Microsoft knowledge base article:
2460049 - Description of Office 2010 SP1
Grouping Objects
The steps provided work best under Word 2010:
After you open the recovered document, turn on the Selection pane. This can be found in the
Home tab of the ribbon. The editing group of the
Home tab has a dropdown button named Select.
Click the Select button, and then click
Selection Pane...
Press the Ctrl button on your keyboard and then click each text box in the selection pane.
Click the Group button under the Format tab. This will group all the objects together.
As soon as you have all objects grouped on each page, save the document under a new name.
Save the document in the .RTF file format
The steps provided work for both Word 2007 and Word 2010:
After you open the recovered document, click File and select
Save (for Word 2007 click the Office button and select
Save As)
In the Save As dialog box, click "Save as type:" dropdown and select
Rich Text format (*.rtf).
Click Save.
Click to view this
blog for more information about this issue.
Bonus tip: Win7 Win8 Math Equation Input Panel / Math input Panel
http://www.lytebyte.com/2009/07/24/guide-to-math-input-panel-in-windows-7/
http://www.7tutorials.com/windows-7s-tablet-input-panel-text-entry-and-handwriting-recognition
http://www.7tutorials.com/training-tablet-input-panel-work-even-better
http://www.7tutorials.com/do-math-easy-way-math-input-panel
Not an answer to the problem, just a bonus that may make it easier to input formula’s in Win7.
Here’s another one of those didn’t-know-it-existed-until-I-clicked-it-by-accident tools in Win7. It’s called the
Math Input Panel.
To access it, simply click Start, and in the Search Box that appears above, type in
Math Input Panel.
The Window should look like this:
Let the fine folks at Microsoft explain what it’s used for:
“Math Input Panel uses the math recognizer that’s built into Win7 to recognize handwritten math expressions. You can then insert the recognized math into a word-processing or computational program. “
Tony Jolan’s Automatic Fix
Download http://www.wordarticles.com/temp/Rebuilder.dotm Microsoft Office Word Macro-Enabled Template (.dotm) and open it.
Click Options button on the Security warning and select Enable this content.
Click the Broken Documents tab at the far right of the ribbon.
Click the Rebuild button in the left-hand side
Locate and open your corrupt document in the file open dialog.
That's it. The process will repair your document if possible and create a new document with (Rebuilt)
appended to the filename. Be patient as it may take a few minutes. If a repair is not possible, you can then post to a public file area and someone here can attempt a manual repair.
Manual Fix
XML Maker V1.1 is free. It will allow you to open the document.xml file and edit it. It also marks errors and warnings.
I just didn’t have much luck working with it.
A poster used XML Maker V2.1 (US$125, 30day free trial, enough for average person to fix a file)
Notepad ++ is a good, free editor for this type of task
Make a copy of the file
Rename the copy from DOCX to ZIP
Open … .ZIP/word/document.xml in notepad
Copy the contents of the file to clipboard
Open Word
Paste a copy of the copied XML into Word
(optional) the XML is one long string too hard to read, you can replace some tags, with that tag plus a para mark to break up the text to make it more people readable.
Open an XML validator, ie this site on the internet:
http://www.w3schools.com/xml/xml_validator.asp
Paste another copy of the XML into the “Syntax Check Your XML” input window
Click on “validate” button
Copy the missing tag, ie </mc:Fallback> (yours will be different)
Return to word Find: mc:Fallback> (without the </ so you find both open and closing tags).
Repeat find until you hit 2 open tags in a row. Then you just have to figure out where to put the closing tag between them.
Look for other tags before and after a proper closing tag so you can match the problem area to a good area.
Discussion by many affected people, a couple in discussions are also fixing problem if Tony’s fix doesn’t work
http://social.answers.microsoft.com/Forums/en-US/wordcreate/thread/581159d0-9ebc-4522-b30c-53e33e8268e1
Document Recovery
http://www.wordarticles.com/Shorts/Corruption/Formats.php
This page has the most readable description of Word file structures, DOC and DOCX, I have seen so far
The logical structure of a Word 97‑2003 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 97‑2003 (.doc) format document:
MyDocument.doc
1Table
*CompObj
Word Document
*SummaryInformation
*DocumentSummaryInformation
The physical structure of the complete file bears little relation to the logical structure; it is, again, of a proprietary design, a compound, or structured storage, file. Briefly, and loosely, the separate logical elements of the file are broken up into
blocks; these blocks are treated as individual units, which units are then organised without regard for their logical arrangement, and catalogued, catalogue and organisation detail being held alongside the blocks themselves, to enable recombination into logical
components when necessary.
Just to give you a flavour, here are some views of three small parts of such a document, viewed in a hex editor:
Views of a Word 97-2003 format Document
The logical structure of a Word 2007 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 2007 (.docx) format:
MyDocument.docx
_rels
rels
docProps
app.xml
core.xml
word
_rels
document.xml.rels
theme
theme1.xml
document.xml
settings.xml
fontTable.xml
webSettings.xml
styles.xml
[Content_Types].xml
As briefly as before, the [Content_Types] file and the _rels folders, along with the subordinate files therein, contain information about the logical structure, and the two files in the docProps folder contain much the same as the two Information files
in the old format. The document.xml element within the word folder holds the bulk of the document content and the other files within that same folder hold formatting details.
So, you might say, the internal structure of a document has changed a little, so what? There are, however, other changes that make a bigger difference. The first is that, although both logical formats are conceptually similar, they are wrapped up in
completely different ways to make a single file. Instead of the proprietary physical structure used for Word 97‑2003 format documents, a fairly standard, and open, Zip Archive format is used for Word 2007 format documents. The second change is that instead
of using obscure binary codes, everything in Word 2007 format documents, well almost everything, is held in XML format.
All data held as XML? In a standard Zip Package? It should be much easier to work with, then? Judge for yourself; here are some views of parts of a Word 2007 format document taken from a hex editor:
Views of a Word 2007 format Document
FreeFileViewer – reads 100+ text, Office, audio, video format file types – Can open some XML tag error files
http://www.freefileviewer.com/formats.html
Can't open Word file due to undeclared prefix, Location: Part: /word/document.xml, Line:91, Column: 49921
The most likely cause of your particular problem is that you are missing a
schema prefix reference within the opening <document ...> XML tag (usually the second one). Different
schema references are required for various types of specialty content. Here is a sample opening <document ...> tag with a large number of various schema prefix codes. If I remove one or two of these, i can reproduce
your error message.
<w:document xmlns:ve="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" xmlns:m="http://schemas.openxmlformats.org/officeDocument/2006/math"
xmlns:v="urn:schemas-microsoft-com:vml" xmlns:wp="http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" xmlns:wne="http://schemas.microsoft.com/office/word/2006/wordml">
It's impossible to blindly say exactly what you are missing but if you post an unadulterated copy of your document to a public file area (as noted above) and post the location back here, someone may be able to help. If you are going to go this route, send
a copy that has not already been subjected to repair attempts.
FWIW, while it may be hard to determine exactly which schema you may be missing, I do not believe that having extras causes any problems.
BTW, you don't actually have to rename the DOCX file extension if you have an archiving program. I use WinRAR and simply
<right-click>, Open With... to expose the archive.

Help for PowerPoint 2007 crash when running embedded SWF file with latest Flash Player?

I have developed in Xcelsius 2008 SP4 a dashboard with only Excel as the source. I output to PowerPoint and then save it as a PowerPoint 2003 PPS file. On more than a few machines that have PowerPoint 2007, PowerPoint crashes when I attempt to run the presentation. This happens only with later versions of Flash Player. I have tried uninstalling/reinstalling the latest Flash Player but it still crashes. However, when I revert back to Flash Player 10.1.159..., in PP 2007 the presentation runs perfectly.
With regard to the error I receive in PowerPoint 2007, it is as follows:
Error Signature:
AppName: powerpnt.exe AppVer: 12.0.6500.5000 AppStamp:49a68f9d
ModName: flash10u.ocx ModVer: 10.3.181.34 ModStamp:4e011a1d
fDebug: 0 Offset: 003a893c
Of note is that this behavior does not happen in PowerPoint 2003 nor does it happen when the file is saved as a SWF and launched directly in the browser on the problem machines.
I have to assume that this has happened to others so any help you could provide would be VERY appreciated.
Thank you

Hello,
on the first glance I see these: data="file:///Macintosh HD/Users/user/Documents/Website/Working.swf", what means the path to your swf file is pointing to your local hard drive which nobody can see except you. Please replace all thes pathes with the correct ones and load up your file(s) again.
If the problem remains, please send a link to your website in question, no matter how it looks like..
Hans-Günter

Smartview 11.1.2.2.310 - Excel 2007 crashes when openning panel

We are upgrading our users from a previous version of Smartview to 11.1.2.2.310
we are finding users on excel 2007 are having problems when attempting to work with a macro enabled workbook and ad hoc query previously setup from the previous version
Excel crashes when we try and select the connection panel screen with the following dialogue message:
"Microsoft Office Excel has stopped working"
we also tried with the macro options turned off
looking for some help, not sure how to resolve this
Any thoughts anyone?
Chaz

Chaz - were you able to find a solution to this? I am experiencing the same thing with Smartview on excel 2007 also and cannot get past it.

Is there a way to prevent Adobe from crashing when ocring multiple documents?

I'm using Adobe Acrobat 9 Standard. I am trying to OCR multiple documents, Adobe crashes when it hits a document that cannot be OCR'd. How can I prevent Adobe from crashing and to skip that document and continue the OCR'ing process with the next document in the list?

Moving this discussion to the Enterprise Deployment for Creative Cloud, Creative Suite forum.

Acrobat crashes when closing a document.

I have developed a simple Acrobat Addin, which adds a menu item and a toolbar button. The active document will be closed when this menu item or toolbar button is clicked.The document is closed using the function "AVDocClose".
Acrobat crashes when AVDocClose is invoked from toolbar button and works fine when invoked from menu item. This happens only when "Show each document in its own window" is checked and in the version 8.0 Professional. Works fine in 7.0. The crash has occured in Acrobat.dll.
Is this crash a known Acrobat issue in 8.0?
OS : Windows XP
Thanks,
Partha

The only plug-ins installed are the default ones that came installed with Acrobat. All of these are developed by Adobe, so i'm assuming your are not referring to these as "3rd party". All custom plug-ins have been uninstalled with the exception of the Stamper sample to test this theory. Quite literally this can be reproduced by adding the following code to the "ToolActivate" method in StamperUI.cpp. This is the method that is wired into both the MenuItem and Button click events by default in this sample. When this code is executed by a MenuItem event, no issue at all. When this code is executed by a button click event, an exception is thrown from Acrobat.exe. Note that the exception is not thrown from the ToolActivate method, it is thrown at some point after this method completes.
AVDoc avDoc = AVAppGetActiveDoc();
if (avDoc != NULL)
AVDocClose(avDoc, true);
As you can see, no objects are being acquired in this code. If AVDocClose is not executed, no issues at all. Although that goes against what i am attempting to do (as a result of a Button click, i need to be able to close the AVDoc).
Any thoughts as to root cause of this issue?
Karl, i really appriciate your assistance! Thanks.

Word 2007 crashes using manual duplex

I must restart PC to get manual duplex to work. I can do 1 print job with the seting on. The 2nd time, Word crashes & continues to crash until I restart the PC.

Hi @aainbc
I'd be happy to to my best to help. I understand Word crashes when you try to manual duplex.
What printer model do you have? How Do I Find My Model Number or Product Number? I see you have another post and mentioned the M1217NFW, is this the printer you are speaking of?
Does this issue occur when you print from other programs? Can you save the file as a PDF and try manually duplexing from your PDF application?
Thanks, I look forward to hearing from you.
Please click the Thumbs up icon below to thank me for responding.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Sunshyn2005 - I work on behalf of HP

Word 2007 crashes when sving a document

Similar Messages

Maybe you are looking for