none
O365 won't edit a DOCX, Word thinks it is fine RRS feed

Answers

  • I went a little further. After eliminating all the other possible elements in settings.xml, the clrSchemeMapping was definitely the culprit in this case. Changing it from:

        <w:clrSchemeMapping w:bg1="light1" w:t1="dark1" w:t2="dark2" w:bg2="light2"/>

    to:

        <w:clrSchemeMapping w:bg1="light1"
                          w:t1="dark1"
                          w:bg2="light2"
                          w:t2="dark2"
                          w:accent1="accent1"
                          w:accent2="accent2"
                          w:accent3="accent3"
                          w:accent4="accent4"
                          w:accent5="accent5"
                          w:accent6="accent6"
                          w:hyperlink="hyperlink"
                          w:followedHyperlink="followedHyperlink"/>

    Made Word Online happy.

    Tom

    • Marked as answer by DavidThi808 Thursday, April 23, 2015 2:48 PM
    Thursday, April 23, 2015 2:02 AM
    Moderator

All replies

  • Hi Dave:

    I have alerted the open specifications team regarding your inquiry. A member of the team will be in touch soon.


    Regards, Obaid Farooqi

    Tuesday, April 7, 2015 11:44 PM
    Owner
  • Hey Dave,

    A couple of questions:

    1. are you opening with Office Online or an on-premise Office Web App version of Word?

    2. How was the docx file created? Do you suspect the file to be corrupt or non-conformant?

    In general, both versions of the Word web app should support docx files just fine but the Office Online version is not covered under the [MS-OI29500] notes.

    I will test this file against the on-prem Office Web App. I already tested with Office Online and it did as you said, it told me to use the standalone Word.

    Best regards,
    Tom Jebo
    Microsoft Open Specifications

    Tuesday, April 7, 2015 11:46 PM
    Moderator
  • Hi Tom;

    This is a DOCX created by our program and yes, the issue is you can't edit it in the online version of O365.

    What's really worrisome is if O365 won't open/edit a document and we have no way to find out what is causing that. We're fine if it ignores some settings - that is a clear limit of O365. But silently failing on a valid DOCX - that leaves us stuck.

    thanks - dave


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

    Wednesday, April 8, 2015 2:31 PM
  • Hi Dave,

    Just an update. I've been working on this quite a bit but am not quite done.
    I found that your bug document was non-conformant. It had a couple of elements in the table styles properties in the word\styles.xml part that are not allowed per [MS-OI29500].

    2.1.247 Part 1 Section 17.7.6.3, tblPr (Table Style Conditional Formatting Table Properties)
    a. The standard states that the bidiVisual, tblLayout, tblLook, tblOverlap, tblpPr, tblStyle, tblStyleColBandSize, tblStyleRowBandSize, and tblW elements are valid children of the tblPr element.
    Word does not allow these elements to be children of the tblPr element.

    2.1.248 Part 1 Section 17.7.6.4, tblPr (Style Table Properties)
    a. The standard states that the bidiVisual, tblLayout, tblLook, tblOverlap, tblpPr, tblStyle, and tblW elements are valid children of the tblPr element.
    Word does not allow these elements to be children of the tblPr element.

    The two elements are tblW and tlbLayout. These are not allowed in tblPr.

    I removed these and the file successfully validated using the Open XML SDK tools (and of course loaded into Word 2013 standalone). However, it still did not load into Word Online or the on-prem Word Web App.

    Therefore, I spent some time using process of elimination with diff's to find the culprit but so far nothing. I'm talking to our WAC folks now. I'll let you know soon what I find out.

    Tom

    Friday, April 10, 2015 6:44 PM
    Moderator
  • Thanks for diving in to this. And this is not going to be fun going forward if the online O365 fails silently and we all have no way to find out why. Hopefully you can encourage the O365 team to have a means to find out why.

    thanks - dave


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

    Friday, April 10, 2015 10:22 PM
  • Hi Tom;

    Any update yet?

    thanks - dave


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

    Wednesday, April 22, 2015 2:19 PM
  • Hey Dave,

    Sorry, I've been working on another issue but will get back to this today. I eliminated the two elements in table styles, then moved on to a couple of other elements that were not identified by validation in the SDK but were identified by turning on ULS logging in the WAC server. However, this still did not prove completely successful as the file still didn't edit. This can be a tedious process of elimination and searching to find the culprit but hopefully, I'll locate the issue soon. ULS logging is helpful if you have an on-prem Office Web App Client server to test with.

    Anyway, thanks for your patience.

    Tom

    Wednesday, April 22, 2015 5:05 PM
    Moderator
  • Hey Dave,

    I started over on the bug document and finally got it to work. I decided to start with one of the elements my on-prem testing with ULS logs identified as a problem. The clrSchemeMapping in the settings.xml part. Taking a look at the settings.xml part from the standalone Word resave of your document, it was obvious I could copy the whole thing. It's not that big and no external references or anything that wouldn't be understood in your package. The clrSchemeMapping element was not complete according to on-prem WAC Word. replacing it with the standalone resave completed it.

    Here is the settings.xml part:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <w:settings xmlns:mc="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:w10="urn:schemas-microsoft-com:office:word" xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" xmlns:w14="http://schemas.microsoft.com/office/word/2010/wordml" xmlns:w15="http://schemas.microsoft.com/office/word/2012/wordml" xmlns:sl="http://schemas.openxmlformats.org/schemaLibrary/2006/main" mc:Ignorable="w14 w15">
        <w:zoom w:percent="100"/>
        <w:proofState w:spelling="clean" w:grammar="clean"/>
        <w:defaultTabStop w:val="708"/>
        <w:characterSpacingControl w:val="doNotCompress"/>
        <w:compat>
            <w:compatSetting w:name="compatibilityMode" w:uri="http://schemas.microsoft.com/office/word" w:val="15"/>
            <w:compatSetting w:name="overrideTableStyleFontSizeAndJustification" w:uri="http://schemas.microsoft.com/office/word" w:val="1"/>
            <w:compatSetting w:name="enableOpenTypeFeatures" w:uri="http://schemas.microsoft.com/office/word" w:val="1"/>
            <w:compatSetting w:name="doNotFlipMirrorIndents" w:uri="http://schemas.microsoft.com/office/word" w:val="1"/>
            <w:compatSetting w:name="differentiateMultirowTableHeaders" w:uri="http://schemas.microsoft.com/office/word" w:val="1"/>
        </w:compat>
        <w:rsids>
            <w:rsidRoot w:val="00856470"/>
            <w:rsid w:val="00856470"/>
            <w:rsid w:val="00A4765A"/>
        </w:rsids>
        <m:mathPr>
            <m:mathFont m:val="Cambria Math"/>
            <m:brkBin m:val="before"/>
            <m:brkBinSub m:val="--"/>
            <m:smallFrac m:val="0"/>
            <m:dispDef/>
            <m:lMargin m:val="0"/>
            <m:rMargin m:val="0"/>
            <m:defJc m:val="centerGroup"/>
            <m:wrapIndent m:val="1440"/>
            <m:intLim m:val="subSup"/>
            <m:naryLim m:val="undOvr"/>
        </m:mathPr>
        <w:themeFontLang w:val="en-GB" w:eastAsia="zh-CN"/>
        <w:clrSchemeMapping w:bg1="light1" w:t1="dark1" w:bg2="light2" w:t2="dark2" w:accent1="accent1" w:accent2="accent2" w:accent3="accent3" w:accent4="accent4" w:accent5="accent5" w:accent6="accent6" w:hyperlink="hyperlink" w:followedHyperlink="followedHyperlink"/>
        <w:shapeDefaults>
            <o:shapedefaults v:ext="edit" spidmax="1026"/>
            <o:shapelayout v:ext="edit">
                <o:idmap v:ext="edit" data="1"/>
            </o:shapelayout>
        </w:shapeDefaults>
        <w:decimalSymbol w:val="."/>
        <w:listSeparator w:val=","/>
        <w15:docId w15:val="{F863AED0-EFFA-4C56-B303-9A5B22B3908F}"/>
    </w:settings>

    I believe the only relevant change is the clrSchemeMapping element but you can trim out some of the other elements in here to be certain. It's not very big.

    The process of finding this can be done without any special tools or logging, it would just take longer. I suggest using a sort of binary search approach to this. Save it with Word standalone first. Then diff the parts and piece by piece, experiment with pulling different elements and values from the resaved document to the buggy one.

    I hope this helps.

    Tom

    Wednesday, April 22, 2015 11:04 PM
    Moderator
  • I went a little further. After eliminating all the other possible elements in settings.xml, the clrSchemeMapping was definitely the culprit in this case. Changing it from:

        <w:clrSchemeMapping w:bg1="light1" w:t1="dark1" w:t2="dark2" w:bg2="light2"/>

    to:

        <w:clrSchemeMapping w:bg1="light1"
                          w:t1="dark1"
                          w:bg2="light2"
                          w:t2="dark2"
                          w:accent1="accent1"
                          w:accent2="accent2"
                          w:accent3="accent3"
                          w:accent4="accent4"
                          w:accent5="accent5"
                          w:accent6="accent6"
                          w:hyperlink="hyperlink"
                          w:followedHyperlink="followedHyperlink"/>

    Made Word Online happy.

    Tom

    • Marked as answer by DavidThi808 Thursday, April 23, 2015 2:48 PM
    Thursday, April 23, 2015 2:02 AM
    Moderator
  • Thank you for figuring this out. I think we're going to have to tell our customers that we don't support the online Word because otherwise we're going to keep seeing issues like this.

    And that settings.xml we just copied from the source DOCX so I'm guessing somehow desktop Word created it that way. This is going to be bad if desktop Word creates files online Word can't read.

    Again, thank you.


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


    • Edited by DavidThi808 Thursday, April 23, 2015 2:54 PM
    Thursday, April 23, 2015 2:50 PM
  • If you copied the settings.xml from a source file, can you share that file with me and tell me what version of Word created it? That would help to understand what caused the problem.

    Tom

    Thursday, April 23, 2015 4:33 PM
    Moderator
  • Will do, if I can. It's one of our customers and I've got to track down what-all around it.

    thanks - dave


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

    Thursday, April 23, 2015 5:44 PM