none
Why is this file very very bad? RRS feed

Answers

  • Dave, 

    After spending some time debugging Word's XML parsing, I was able to find one problem that Word doesn't like. You had nested <Relationship> tags. This is not allowed. Relationship elements can't have child Relationship elements. The word\charts\_rels\chart1.xml.rels had this block: 

    <?xml version="1.0"?>
    <Relationships xmlns="http://schemas.openxmlformats.org/package/2006/relationships">
      <Relationship Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/package" Target="../embeddings/Windward_ChartData_1.xlsx" Id="rId3">
        <Relationship Id="rId2" Type="http://schemas.microsoft.com/office/2011/relationships/chartColorStyle" Target="colors1.xml"/>
        <Relationship Id="rId1" Type="http://schemas.microsoft.com/office/2011/relationships/chartStyle" Target="style1.xml"/>
      </Relationship>
    </Relationships>

    Notice the bolded "Relationship" elements. 

    Unfortunately, Word still isn't opening the document so I think there are yet more issues. This will take some more time and could involve multiple iterations. 

    Thanks,

    Tom

    • Marked as answer by DavidThi808 Saturday, April 6, 2019 4:41 AM
    Saturday, April 6, 2019 2:12 AM
    Moderator

All replies

  • Hi Dave, 

    I'll take a look at the file and see if I can identify a problem. Do you have any ideas what area of the format might be in question with this example? 

    Best regards,
    Tom Jebo
    Sr Escalation Engineer
    Microsoft Open Specifications


    Sunday, March 24, 2019 10:18 PM
    Moderator
  • Hi Dave,

    With Word for Android, I could see/open a Word document you'd shared.
    But I could not with Word 2016 for Windows. Word for Windows says it is corrupted.
    Which Word are you using?

    Regards,

    Ashidacchi -- https://ssl01.rocketnet.jp/hokusosha.com/default.html

    Sunday, March 24, 2019 10:43 PM
  • Hi Dave,

    Your file might be recovered. Please download "ATE-1440_recovered.docx" via OneDrive.

    Regards,

    Ashidacchi -- https://ssl01.rocketnet.jp/hokusosha.com/default.html

    Sunday, March 24, 2019 10:49 PM
  • Hi Tom;

    I'm using Windows desktop Word 2016 - latest update.

    thanks - dave


    What we did for the last 6 months - Made the world's coolest reporting & docgen system even more amazing

    Sunday, March 24, 2019 11:00 PM
  • Hi Ashidacchi;

    Unfortunately recovering it doesn't help - the problem for me is why is it bad. My code created it and I have to figure out what I need to do differently.

    thanks - dave


    What we did for the last 6 months - Made the world's coolest reporting & docgen system even more amazing

    Sunday, March 24, 2019 11:01 PM
  • Hi Dave,

    Sorry, I don't have answer about WHY.  I'm afraid you need to provide your code.

    Regards,

    Ashidacchi -- https://ssl01.rocketnet.jp/hokusosha.com/default.html

    Sunday, March 24, 2019 11:22 PM
  • Dave, 

    After spending some time debugging Word's XML parsing, I was able to find one problem that Word doesn't like. You had nested <Relationship> tags. This is not allowed. Relationship elements can't have child Relationship elements. The word\charts\_rels\chart1.xml.rels had this block: 

    <?xml version="1.0"?>
    <Relationships xmlns="http://schemas.openxmlformats.org/package/2006/relationships">
      <Relationship Type="http://schemas.openxmlformats.org/officeDocument/2006/relationships/package" Target="../embeddings/Windward_ChartData_1.xlsx" Id="rId3">
        <Relationship Id="rId2" Type="http://schemas.microsoft.com/office/2011/relationships/chartColorStyle" Target="colors1.xml"/>
        <Relationship Id="rId1" Type="http://schemas.microsoft.com/office/2011/relationships/chartStyle" Target="style1.xml"/>
      </Relationship>
    </Relationships>

    Notice the bolded "Relationship" elements. 

    Unfortunately, Word still isn't opening the document so I think there are yet more issues. This will take some more time and could involve multiple iterations. 

    Thanks,

    Tom

    • Marked as answer by DavidThi808 Saturday, April 6, 2019 4:41 AM
    Saturday, April 6, 2019 2:12 AM
    Moderator
  • Tom;

    First off thank you. That is bad and I'll fix it.

    For the rest, you can stop on this. I reverted back to some previous code that is correct and worked from that. So we're good now. And no point in tracking down what weird little difference causes this if we no longer need to know.

    Again, thank you for working on this.

    thanks - dave


    What we did for the last 6 months - Made the world's coolest reporting & docgen system even more amazing

    Saturday, April 6, 2019 4:41 AM
  • Hey Dave, 

    Thanks for the explanation. I won't dig further. 

    Tom

    Saturday, April 6, 2019 11:24 PM
    Moderator