HTML Preview on DOCx document gives an erros

Question

Hi I just wanted to do a HTML preview of the SamplePhotoPrinter.doc file which I saved as docx and I got an error. Could not load file or assembly 'OpenXmlPowerTools, Version=4.5.3.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I'm sure this was working in the past. Could it be it is related to the update of Open XML SDL as per https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380 ? I attach the image and the log. Fullscreen 1070.sdlerror-2017928-17h55m48s.sdlerror.xml Download Could not load file or assembly 'OpenXmlPowerTools, Version=4.5.3.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) System.IO.FileLoadException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 OpenXmlPowerTools, Version=4.5.3.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Sdl.FileTypeSupport.Filters.MicrosoftOffice_2 -2146234304 SDL Trados Studio 14.0.0.0 14.1.6329.7 Microsoft Windows 7 Professional Service Pack 1 1033 1250 4.0.30319.42000 True 8078840 MB

Paul · Accepted Answer

Hi Simon Bratina , 
 
This is a known issue with a simple fix. Maybe the next CU... although this needs confirming. I can give you a fix for this now if you like but it will mean you'll have to remember you applied the fix and undo it when we do provide an update so the update won't work properly. 
 
Regards 
 
Paul

Paul · Answer

Hi Tomoyuki Kono , 
 
As I mentioned above we know about this and will fix it in a future update. Thanks for the additional information though just in case it's useful for development. 
 
Regards

Michael Beijer · Answer

Looking forward to the fix here too!

Paul · Answer

Unknown said: SDL&rsquo;s developers need to admit that the new versions of Office are not going to change, and that the Embedded preview system will simply have to be rewritten so it works anyway. Btw, can't something be cobbled together using one of the open source Office programs? 
 Hi Michael Beijer 
 First of all, take a look at this: 
 
 I'm running Studio 2017 with Office 2016, a click to run installation. The problem we will continue to have is that the embedded preview will no longer work because Word doesn't include the hooks we need to include this. However, as you can see in the video we can use Word as a realtime preview and also HTML. 
 There are a few things to note however: 
 
 If you have click to run or anything other than the older MSI based installations (like me) then don't click on "Embedded" as this will not work 
 If you do click on "Embedded" then the Word preview will no longer work either. You need to reopen the file and go straight to the Word preview. I'm pretty sure this will work for you as long as you are using the new Word filetype. This was not possible with the older one which is just another reason for us moving away from it 
 The "HTML" won't work for you because we included the incorrect OpenXML SDK installer with Studio. A silly mistake on our part. This will be corrected in a future update to Studio. I could let you have a file that will fix this but it will mean when we update you'll have to remove it first or Studio won't update correctly. Your call... just let me know if you want to try it or not? I installed it which is why I could show the "HTML" working 
 
 So in a nutshell we have addressed this preview issue in a smart way I think, so no need to cobble anything together. Just very unfortunate that we then let ourselves down, and you, by not including the appropriate updates in the installer. In fact you'll find all the Office filetypes, if you use the new ones, now support this. I hope this explains the situation for you? 
 Regards 
 Paul

Paul · Answer

No surprises there ... see point 3. above.

Paul · Answer

Unknown said: I don't hear any comments regarding this from SDL and, like I said it before, denial is not a river in Africa. 
 Indeed, and reading is not a town in England. Maybe you are not filtering on all the responses and the rest of us are having a jolly conversation by ourselves?

Paul · Answer

Hi Michael Beijer 
 Unknown said: That's one reason why I like the Embedded preview so much: you don't waste all that space with all the other MS word crap (buttons, etc.). From a non-coder&rsquo;s perspective, it seems that this should be relatively easy to do. But then again, if it were so easy, you probably already would've done it, right? 
 Right. I discussed it briefly with the development team and they have explained that the way we achieved this was by using DSOFramer Control which is something Microsoft provided in the past. Today it's not supported anymore and you can't even download it from the Microsoft website. Without this control it's not possible to embed the preview with an instance of Office and with this control you can't embed a version of Office that is not fully installed (the old MSI installer). So today, with the convenience of the Click to Run installer we lose out on features like this. 
 Hope that makes sense? 
 Regards 
 Paul

Trados Studio > 1. Trados Studio

HTML Preview on DOCx document gives an erros