• State Verified Answer
  • Replies 16 replies
  • Answers 6 answers
  • Subscribers 434 subscribers
  • Views 8127 views
  • Users 0 members are here
Options
Related

HTML Preview on DOCx document gives an erros

Simon Bratina

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 
<SDLErrorDetails time="28.9.2017 17:55:53">
  <ErrorMessage>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)</ErrorMessage>
  <Exception>
    <Type>System.IO.FileLoadException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <FileName>OpenXmlPowerTools, Version=4.5.3.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</FileName>
    <FusionLog>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].
</FusionLog>
    <HelpLink />
    <Source>Sdl.FileTypeSupport.Filters.MicrosoftOffice_2</Source>
    <HResult>-2146234304</HResult>
    <StackTrace><![CDATA[   at Sdl.FileTypeSupport.Filters.MicrosoftOffice.Preview.Word.Html.DocxToHtmlConverter.ConvertToHtml(String docxInputFilePath, String outputHtmlFilePath, String outputHtmlFileContentFolder)
   at Sdl.FileTypeSupport.Filters.MicrosoftOffice.Preview.Word.Html.DocxToHtmlFileManager.ConvertDocxToHtml()
   at Sdl.FileTypeSupport.Filters.MicrosoftOffice.Preview.Word.Html.HtmlInternalPreviewController.Refresh()
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.ShowControlPreview(IManagedPreview preview)
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.jobRequest_PreviewGenerated(ITranslatableDocument document, IManagedPreview activePreviewType, PreviewTempFileGenerator tempFileGenerator, GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.GeneratePreviewJobRequest.AfterExecute(IJob job)
   at Sdl.Desktop.Platform.Implementation.Services.Job.FinalizeJob()
   at Sdl.Desktop.Platform.Implementation.Services.JobService.ExecuteJobWithProgress(IExecutableJob job)
   at Sdl.Desktop.Platform.Implementation.Services.JobService.ScheduleJob(IJobRequest jobRequest)
   at Sdl.TranslationStudio.Editor.Previews.ViewPreviewManager.GeneratePreview(PreviewSetInfo previewSetInfo, GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.PreviewManager.GeneratePreview(GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.PreviewManager.RegeneratePreview(GenerateType generateType)
   at Sdl.TranslationStudio.Editor.Previews.InternalPreview.InternalPreviewViewPart._waitingRefreshControl_RefreshClicked(Object sender, EventArgs e)
   at Sdl.TranslationStudio.Editor.Previews.InternalPreview.WaitingRefreshControl.FireRefreshClickedEvent()
   at Sdl.TranslationStudio.Editor.Previews.InternalPreview.WaitingRefreshControl.linkLabelRefresh_LinkClicked(Object sender, LinkLabelLinkClickedEventArgs e)
   at System.Windows.Forms.LinkLabel.OnLinkClicked(LinkLabelLinkClickedEventArgs e)
   at System.Windows.Forms.LinkLabel.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Label.WndProc(Message& m)
   at System.Windows.Forms.LinkLabel.WndProc(Message& msg)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.6329.7</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 7 Professional </OperatingSystem>
    <ServicePack>Service Pack 1</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1250</CodePage>
    <LoggedOnUser></LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName></ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8078840 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi ,

    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 Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Hi Paul,

    Thank you for the explanation.

    As this issue came up as part of custom file type preview options question I'd say we can wait. There are still other options we can use in the meantime.

    Thank you

    Simon
  • 0 in reply to Paul
    Dear Paul,

    I'm sorry to cut in but I too am facing this issue. In the error log, there is something about editing a registry value but I don't want to risk breaking either SDL Trados Studio or MS Office:

    <FusionLog>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].
    </FusionLog>

    I don't even know if this will fix the issue.
    It's very frustrating because (1) the HTML preview option has never worked for me with any documents because of the error mentioned above; (2) Embedded preview has never worked for me because I have Office 365 Business Pro subscription, which I have been informed is incompatible with this feature and (3) the preview in external Word seems to be very power-hungry and my computer heats up an awful lot/battery drains very quickly when I use this function.

    I don't have issues with live previews in other CAT tools like memoQ, Memsource or Wordfast Pro (OK, the one in WFP is still half-baked, but it does work).

    Please fix this. Live Preview, at least of MS Word files, is nowadays de rigueur, not a desideratum, in my opinion.
  • 0 in reply to Tomoyuki Kono
    Hi ,

    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

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Tomoyuki Kono

    It's getting more and more absurd that SDL Studio just doesn't work with the version of Office 90% of its users will have installed on their computers.

    I understand by now that it is due to the technical nature of Office 365, and yet, after several years of waiting, what are we as users to make of that? Luckily, I always have an ancient copy of Word 2010 lying around somewhere, which I install side-by-side with Office 365 (aka Office 2016). This fixes Studio's broken Embedded preview, and makes it work as it should do for all of us.

    Has SDL done a survey on what versions of Word most of its users have? I am very curious how many users of SDL Studio 2015/2016/2017 have actually ever seen the Embedded preview work. I can tell you: it works beautifully … if you have an ancient installer version of Office 2010 on yr PC ;-)

    SDL’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? 
  • 0 in reply to Michael Beijer

    Unknown said:
    SDL’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  

    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:

    1. 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
    2. 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
    3. 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 Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • Former Member
    0 Former Member
    I've just got this minute exactly the same error during the same operation (HTML preview).
  • 0 in reply to Former Member
    No surprises there ... see point 3. above.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Hi Paul,

    Having just watched your video again, and seeing how well the external word preview works, I had an idea (as usual). How hard would it be to ‘frame’ the MS Word external preview inside of Studio? That is, there must be some way to add it to the UI of Studio, integrated that is, to make better use of limited screen space.

    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’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?

    I know that there are all kinds of tricks that you can do with AHK + MS Word, via that "COM" stuff, such as manipulating MS word text  from another program using AutoHotkey and without having to bring MS Word to the foreground, etc.