Error message: The document cannot be processed since it contains unexpected contents.

This is a mystery I'd like to solve if anyone has an idea: this .docx cannot be processed in Studio 2017 and there is no other explanation other than this error message. Someone else had a similar problem, I saw, and was able to process the document in Studio 2015, so I tried the same solution. It worked! After converting the file into .sdlxliff in Studio 2015, I was able to open it in Studio 2017 and continue processing it with no problems.

But I'd like to hear any ideas as to what might be causing the problem and what to do in the future if using Studio 2015 doesn't work? It's frustrating not knowing what kinds of issues are involved with this error message.

(By the way, I tried copying and pasting the contents of this file into a new .docx file but that did not work. I don't see any formatting issues in this .docx that aren't in its other 6 companion files, all created on the same day using the same methods and computer.)

Cheers and thanks!

Zakiya

Parents Reply Children
  • Right, I find that using the earlier Word 2007-2016 filetype as you suggested allows me to process this file in Studio 2017. Thank you for the workaround!

    This doesn't answer the question why this particular file is giving trouble with the WordprocessingML v.2 filetype, though, when used in Studio 2017.

    Please note that when I open the "bad" file with Studio 2015 using the WordprocessingML v. 2 filetype it works just fine. Also, I originally created 7 files at the same time, all using the same Word template. They all work fine with the WordprocessingML v. 2 filetype except this one particular file.

    (By the way, I don't really want to revert to the earlier Word 2007-2016 filetype unless I have to, because then I can't have real-time Word previews while I'm working, which is such a great feature.)

    These screenshots show the "bad" file in Studio 2015 as a Wordprocessing ML v. 2 file type and with Project Settings (and Options) checked only for Word 2007-2016 and yet it works fine.

  • Just happened to me too. MemoQ handled the file no problem, like all the other files Trados had problem with. Effectively ruined the repetitions yield in the project. Screw it, Trados is the last SDL product I ever bought. Would've stuck with 2011 if not for DeepL.