Unspecified Error, word/document.xml, Line:2, Column: 0

There was a rogue <m:ctrlPr/> XML tag that was gumming up the works. The document opened conventionally as soon as I removed it.

I do not believe that any content was lost but you will want to check the formulas just above the phrase "The directivity is just the radiated power density in that direction [...] " on page 2 (of 13).

I've uploaded the repaired DOCX to my SkyDrive here.

ECEN 638 HW2 - Jeeped.docx

I am having the same issue. Word 2007 lists the location as Line 2, Column 47461. I'm not sure how to go about removing any problem areas and then resaving it though.

I've tried uploading the file to skydrive.

https://skydrive.live.com/redir?resid=2A8AF368AAA78AC6!107&authkey=!ACYXSpNR4sbvh8E

Hopefully the link works, this is the first time I've ever used sky drive.

Thanks for the clarification.

The point you made, that is clear from the cries of pain we see posted, the changes are all too often happening near the end of the writing process. Minor edits.  This highlights another preventative measure. Making frequent "incremental" file copies. The following tools and macros add functionality that Word / Office! is still missing, doing true "autosaves" (NOT autorecover!) and optionally adding timestamps to the autosaves. 

Sure Graham's "Autohistory" tool creates a lot of "clutter", apparently unneeded, wasted space, extra copies of the files. But at least you have the option of cleaning them up when you don't need them, AND they are there when you DO need them. At the last minute disasters we are seeing posted! That is why I like the tool so much and set the interval to 5 minutes when I'm working on "important" documents.  I just have to remember to periodically go back an prune out extra copies I know I no longer need. I typically start by keeping just the full hour copies. farther back I keep just 2 or 3 copies per day and even farther back, just one copy per day.

Autohistory for Word 2007 / 2010, Excel 2010 (Version Control)

https://autohistory.codeplex.com/

(equivalent to GMayor tool) Creates a Date&Timestamped copy of file every time you perform a normal Save. You can access any of the older versions. It creates a folder for each document affected. You have to the option of creating a single “universal” backup location.  The History is located in a NEW GRROUP on the View Tab.

Automatically backup Word documents

http://www.gmayor.com/automatically_backup.htm

Graham has created an addin that does something MS should have done 20+ years ago.

<snip>

Contrary to popular opinion, Word has no integral means of automatically saving the current document, nor of backing-up the current document. What it does have is an option to save AutoRecover information after a specific and configurable interval and an option to save a backup copy of the previously saved version of the document with the default file extension of WBK (and although there is no reason to do so, Word also allows the option to change this extension to the user's choice). This is not a true backup in as much as it is not a copy of the current version of the document.

A function to create a true automatic backup is provided by the **Save In Two Places add-in which is detailed in a separate page**, There is also available from this web site a complementary add-in which provides numbered versions of a document. **Again that has its own web page.**

</snip>

Save Numbered Versions Add-In for Word 2007 & 2010

http://www.gmayor.com/SaveVersionsAdd-In.htm

Save Numbered Backup Versions of Document

http://www.word.mvps.org/FAQs/MacrosVBA/SaveIncrementedFilename.htm

Save Dated & numbered Backup versions of a document - Word

http://www.gmayor.com/save_numbered_versions.htm

Saving Everything Macros

http://word.tips.net/T001469_Saving_Everything.html

Summary: Need to force users to save their work? It may be as simple as implementing an AutoNew() to force every new file to have a filename, and an AutoClose() to save the current document BEFORE closing. It could, however, also have something to do with training users.

Controlling Names of Backup Files

http://wordribbon.tips.net/T011760_Controlling_Names_of_Backup_Files.html

Save the current document in two locations add-in for Word 2007 & 2010

http://www.gmayor.com/SaveInTwoPlacesAddIn.htm

Performs a normal save in one location, then does a DOS copy to the second location (ie USB)

Making Backups as You Work

http://www.informit.com/articles/article.aspx?p=731710&seqNum=5

Win8 Tip: Enable File History

http://www.winsupersite.com/article/windows8/windows-8-tip-enable-file-history-143579

... so if he says to not edit equations, I'd pay close attention.

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 (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.