Can't open Word File because of end tag/start tag mismatch error...need XML help!

Anonymous
2010-06-09T00:42:38+00:00

I get the following message when i try to open a word document that i desperately need

  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: 96760

I know how to "unzip" the docx files and get to the main document.xml file, but i know nothing about xml programming. Any suggestions? i got an xml editor and found that there are 6 mismatch errors, but i don't know how to fix them. I also don't know how to rezip al the files back into a docx format. I would love any help. Thanks.

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-04-25T16:26:25+00:00

You're welcome Catherine.

Going forward if you or anyone else comes across this issue again, we have a FixIt solution created that should address this problem.  You can go to the following KB article and it should give you the details about how you can correct these documents.

http://support.microsoft.com/kb/2528942

Brandon

Was this answer helpful?

5 people found this answer helpful.
0 comments No comments

528 additional answers

Sort by: Most helpful
  1. Anonymous
    2011-09-01T21:16:28+00:00

    No worries and thanks for the kind comments.

    You will want to proofread that document as best you can. A search for the following sentence,

    Al día siguiente Max, Carlos y Anale esperaban en la plaza donde aterrizaron con el ave gigante el día anterior, la cual se habían enterado era la plaza de

    ... should show missing text as that was where code and text merged. I believe it is on page 398, e.g. the last page I was able to recover.

    I've removed the file from my SkyDrive. Make a couple of backups!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-09-01T20:48:36+00:00

    DUDE! YOU ARE AWESOME!

    Next time you're down here at El Paso, call me up. Beers are on me ;-)

    You can take it down now. I downloaded it.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-09-01T20:18:36+00:00

    Can it be fixed?

    Apparently it can. I was able to guess the correct sequence of ending codes to get a working document of 398 pages.

    I've uploaded the Kildea_repaired.docx to my SkyDrive here. Click on File in the upper left for download options. Let me know when I can remove it from public access.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-09-01T19:57:34+00:00

    Can it be fixed? It would save me a buttload of trouble.

    Thanks for the prompt response. I've located and fixed the original trouble and now I'm trying to apply ending tags that were truncated off so that the document think of itself as intact and open up in Word. The original problem was at line 2, column 3636973 where the tag

    <w:p w:rsidR="00DA76AE" w:rsidRDefault="00DA76AE" w:rsidP="00DA76AE">

    ... got truncated to rsidP="00DA76AE" and merged with the previous sentence. I'll keep at this for a while and see if I can get the repair to a point that it will open.

    Was this answer helpful?

    0 comments No comments