We've recently noticed an issue where documents are becoming corrupt after making edits and saving the file. There have been multiple forum threads related to this particular issue and the purpose of this blog is to try and give you some ideas for how to correct the problem.
The one disclaimer worth mentioning is that this is not a 100% fix for all corrupt documents, nor will it fix all documents that give you the specific error message noted below. The idea is to try and give you some options for getting your document back to a state where you can make edits/changes.
Problem Description:
Opening a Word document gives you an error "The file <filename> cannot be opened because there are problems with the contents.
The name in the end tag of the element must match the element type in the start tag. Location: Part: /word/document.xml, Line: 2, Column: 129414"
If you came to this blog from the FixIt KB article http://support.microsoft.com/kb/2528942, you can use the steps below to try and edit the document so that the issue does not keep re-occurring when you make more edits to the document and save the file. After running the FixIt you should be able open the document in Word without getting an error message.
The problem however, still remains in the structure of the document. Typically it's somewhere in an equation or a textbox. If you make any edit to the document that doesn't correct the behavior and you save the document, you will end up with the document still giving you the error message. It's important to keep in mind that the FixIt solution won't prevent the problem from re-occurring. It can only put the document into a state where Word will be able to open the document.
Next, we get to the workarounds and if you didn't get to this blog post from the KB article, you can go to the article referenced above and run the FixIt solution to correct the document. The KB article also has more information about this particular issue. Once you have the document in a state where you can open it in Word, you can then proceed to the workarounds to try and correct the document.
Possible Workarounds:
Lastly, there have been a lot of forum threads related to this particular problem and I would like to say a huge "Thank You!" to the MVP's and everyone else who has been helping people get their documents fixed.