• State Verified Answer
  • Replies 16 replies
  • Answers 6 answers
  • Subscribers 433 subscribers
  • Views 7766 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
Parents
  • Former Member
    0 Former Member

    Looking at this log file I can't help but notice that your PC (still) has Windows 7 (an operating system which is 10+ years old), which makes me think if SDL is bending over backwards to be backward-compatible (no pun intended). Incidentally, I've noticed in a number of Webinars that the presenters still use Windows 7 (!) My point, and my suspicion, is that Studio 2017 SR1 is still dragging old, and probably irrelevant, legacy code in newer versions, instead of an actual revamp or at least a streamlined code base, each time a new iteration is released to the public. Thus, its sluggishness and slowness sometimes, plus random "error messages" here and there. I don't hear any comments regarding this from SDL and, like I said it before, denial is not a river in Africa. Warm regards.
  • 0 in reply to Former Member

    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 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 in reply to Paul

    Dear Paul, are you suggesting that the mere fact of (judiciously) "filtering on all the responses" will solve actual problems and legitimate concerns from a SDL customer or customerS, for that matter? In addition, most of those 'suggestions' are useless, if you allow me this time, again, to be candid. It's not only me. I already gave my two cents, full of details, with no counterarguments or just simply real solutions. But if all I'm getting is a tongue-in-cheek response, instead of actual and useful solutions, I'm going to start questioning my loyalty to SDL. Let me resort to a cliché in the customer service realm: "The customer is always right". It is not just about technology, it is about people (trying to enjoy without hassles that technology). There are cautionary tales aplenty techcrunch.com/.../
Reply
  • Former Member
    0 Former Member in reply to Paul

    Dear Paul, are you suggesting that the mere fact of (judiciously) "filtering on all the responses" will solve actual problems and legitimate concerns from a SDL customer or customerS, for that matter? In addition, most of those 'suggestions' are useless, if you allow me this time, again, to be candid. It's not only me. I already gave my two cents, full of details, with no counterarguments or just simply real solutions. But if all I'm getting is a tongue-in-cheek response, instead of actual and useful solutions, I'm going to start questioning my loyalty to SDL. Let me resort to a cliché in the customer service realm: "The customer is always right". It is not just about technology, it is about people (trying to enjoy without hassles that technology). There are cautionary tales aplenty techcrunch.com/.../
Children
  • 0 in reply to Former Member
    Dear ,

    You have responded into this thread where I had advised already what the situation was and that we are awaiting a fix, probably in the next update, for this preview problem. You then said I had not responded when I clearly had. This led me to believe you had not read the response.

    I'm wondering if you are even responding to the same conversation we are having in here because I'm not at all clear. If I summarise the discussion this is what I take from it:

    1. The html preview for DOCX is not working for Simon (or anyone else with the latest version of Studio)
    2. I explained why and advised we will release a fix, probably in the next update
    3. Michael told us how he uses the old Office 2010 MSI installer to achieve a realtime preview and wondered if it was possible at all with the click to run installers we see today
    4. I showed the preview working, but I could only do this because I had used a solution that should have been installed with the last update. This is the fix I mentioned to Simon
    5. You said you had the same problem with the HTML preview not working. This isn't surprising given the discussion that had already taken place
    6. Now you bring in a discussion on old Windows technology and say you have seen no response from SDL. This is the first time in this thread I have seen this mentioned so I'm assuming you are referring to this thread, seeing as you posted it here, and where we have responded quite a bit. Are you referring to somewhere else?

    You also mention presenters still using W7. I don't really know what to make of that or what you have been watching. But our development team probably all use W10, and SDL as a rule have not extended past W8.1 because as a Corporate the automatic updates is something I believe we are not ready to deal with. It may be something else, I haven't really looked into that, but I think most of our non development team use W8.1. Maybe there are some still on W7, I have no idea but if they are it has no bearing on the reason for our code and they should probably upgrade as W7 is no longer supported by Microsoft anyway..

    I also doubt anyone is going to completely refactor a codebase as large as Studio each time there is a major windows update. In the ideal world it would be great, but it's not practical or achievable without doing it at a loss. So we do what we need to while working on things for the future at the same time that will eventually replace what we use today.

    My own view on our relationship in this community is that we try to be as open and honest as we can. I like the community to be this way rather than always taking the corporate stance and never giving anything away. If we are wrong and need to address something then we'll do it. I'm sure it won't always be as rapid as people might like, but we do our best. I don't believe the customer is always right, but I'll refrain from making any more quips to compete with yours. Clearly I completely misread your mood... apologies for that.

    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