Error message while reconverting file back to Word

Hello,

Sorry I have to come back to you because of still persisting error messages while reconverting my translated files back to Word. Please find below the full error message. I would be very grateful if you could help me out, because I already tried the "Translate single document process" and everything that I was able to think about.

When Trados one time lets me create the Word document, the language suddenly turns back to the source language in the target... It seems as these two problems are linked to each other.

Thanks a lot for your support!

Susanne

<SDLErrorDetails time="27.04.2016 18:03:07">
  <ErrorMessage>An error occurred while converting fields back to Microsoft Word format.</ErrorMessage>
  <Exception>
    <Type>Sdl.FileTypeSupport.Framework.FileTypeSupportException, Sdl.FileTypeSupport.Framework.Core, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888</Type>
    <HelpLink />
    <Source>Sdl.FileTypeSupport.Framework.Adapter.Framework1</Source>
    <HResult>-2146233088</HResult>
    <StackTrace><![CDATA[   bei Sdl.FileTypeSupport.Framework.Adapter.Framework1.AbstractFramework1Adapter.ReThrowFilterFramework1Exception(Exception* x)
   bei Sdl.FileTypeSupport.Framework.Adapter.Framework1.Writer.EndOfInput()
   bei Sdl.FileTypeSupport.Framework.Integration.NativeWriterMessagesProxy.EndOfInput()
   bei Sdl.FileTypeSupport.Framework.Integration.FileGenerator.CallEndOfInput()
   bei Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
   bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
   bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.OnEndFile()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.<ContinueScanning>b__2(ISdlXliffStreamContentHandler handler)
   bei System.Collections.Generic.List`1.ForEach(Action`1 action)
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ContinueParsing()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   bei Sdl.ProjectApi.AutomaticTasks.NativeFileGenerator.GenerateFiles(ContentRestriction restriction, Boolean preview, Int32 filePercentBase, Int32 filePercentFactor)
   bei Sdl.ProjectApi.AutomaticTasks.GenerateTargetTranslation.GenerateTargetTranslationTask.ProcessFile(IExecutingTaskFile executingTaskFile)
   bei Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>11.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>11.2.4435.12</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>Susi\SUSI</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>SUSI</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>4114728 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Parents
  • If you run the F8 check and NO tag issues are reported, so your source file is damaged.
    Should there be any tag issues reported, correct those and the problem will be gone.
    If not (what I suppose here), your source document contains a field, which hasn't been fully deleted (like a TOC). Please open the file in Word, press CTRL+A and then F9 to update fields. Save Word. Then you should be able to find and delete the damaged field. If that does not help, save as DOCX instead of DOC (or the other way round) and try again.
    If even this does not help, open again in Word, press CTRL+A and CTRL+SHIFT+F9. Save Word and try again.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • Dear Jerzy,

    Thank you for your support. I tried almost anything.... and could finally reconvert to Word after having run the tag check (all messages were related to deleted or added spaces which were correct in my German target language) - there were no fields missing. I also checked the source word document for hidden or not fully deleted fields, finally saved the Word doc under a different file type as you said and then reconverted it into Trados with the single file workflow .... pretranslated it (as I already did 1000 times before) and had to correct manually all tags with color marking which had not been placed correctly ..... (1 hour of word with certainly still a lot of formatting issues to check after printing it out) . Perhaps, this was the solution.
    The problem is that I still don't know what the root cause is. Because by using the single file workflow and creating the target immediately without even translating there is no error message (this was to check if the source file is damaged). Only after pretranslating I get either the above mentioned error message that the target cannot be created or I get a target document in which within a segment it switches back to the source language (after the first 5 pages). Your recommendation with copying the source segments before and after the concerned segment to the target, etc. did not work this time.
    I think it is really a problem with the source text which has so many tags, colors and grafics who corrupt the process of finalizing the file. I also could fix the problem in two other chapters by splitting the file in two separate documents which I passed through the single workflow procedure separately. Only this time that didn't work either.
    My book isn't finished yet and I'm almost sure that I will have the same problem with the next chapter again.

    So, do you have an advice how I can avoid these additional and annoying work which nearly drives me crazy?

    Thank you so much!

    Susanne
Reply
  • Dear Jerzy,

    Thank you for your support. I tried almost anything.... and could finally reconvert to Word after having run the tag check (all messages were related to deleted or added spaces which were correct in my German target language) - there were no fields missing. I also checked the source word document for hidden or not fully deleted fields, finally saved the Word doc under a different file type as you said and then reconverted it into Trados with the single file workflow .... pretranslated it (as I already did 1000 times before) and had to correct manually all tags with color marking which had not been placed correctly ..... (1 hour of word with certainly still a lot of formatting issues to check after printing it out) . Perhaps, this was the solution.
    The problem is that I still don't know what the root cause is. Because by using the single file workflow and creating the target immediately without even translating there is no error message (this was to check if the source file is damaged). Only after pretranslating I get either the above mentioned error message that the target cannot be created or I get a target document in which within a segment it switches back to the source language (after the first 5 pages). Your recommendation with copying the source segments before and after the concerned segment to the target, etc. did not work this time.
    I think it is really a problem with the source text which has so many tags, colors and grafics who corrupt the process of finalizing the file. I also could fix the problem in two other chapters by splitting the file in two separate documents which I passed through the single workflow procedure separately. Only this time that didn't work either.
    My book isn't finished yet and I'm almost sure that I will have the same problem with the next chapter again.

    So, do you have an advice how I can avoid these additional and annoying work which nearly drives me crazy?

    Thank you so much!

    Susanne
Children
No Data