• State Verified Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 4113 views
  • Users 0 members are here
Options
Related

An error occurred while parsing EntityName, Line 1, position 72847

Celestino Genovesi

Hi there,

I'm having trouble finalize a .doc file.

Here the error log:

Fullscreen sdlerror-2020122-18h3m29s.sdlerror.xml Download 
<SDLErrorDetails time="22/01/2020 18:03:33">
  <ErrorMessage>Failed to save target content: An error occurred while parsing EntityName. Line 1, position 72847.</ErrorMessage>
  <Exception>
    <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <LineNumber>1</LineNumber>
    <LinePosition>72847</LinePosition>
    <SourceUri />
    <HelpLink />
    <Source>Aspose.Words</Source>
    <HResult>-2146232000</HResult>
    <StackTrace><![CDATA[   at Aspose.Words.Document.(Stream , LoadOptions )
   at Aspose.Words.Document.(Stream , LoadOptions )
   at Aspose.Words.Document..ctor(String fileName, LoadOptions loadOptions)
   at Sdl.FileTypeSupport.Filters.Doc.DocPostTweaker.Tweak(INativeOutputFileProperties outputFileProperties)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.NativeApi.AbstractFilePostTweaker.TweakFilePostWriting(INativeOutputFileProperties outputFileProperties)
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.ExecuteTweakers(PostGenerationMessageReporterAdapter messageAdapter)
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.RunPostWritingOperations()
   at Sdl.FileTypeSupport.Framework.Integration.FileGenerator.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.FileComplete()
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.FileComplete()
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.FileComplete()
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkFileContainerField* field)
   at FrameworkFileContainerField.vv_AcceptFrameworkVisitor(FrameworkFileContainerField* , FrameworkFieldVisitor* visitor)
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_VisitStartEndField(TmfcReaderImpl* , StartEndField* startEnd)
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.b_VisitNext(TmfcReaderImpl* )
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReader.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
   at Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
   at Sdl.TranslationStudio.Editor.TranslationEditor.SaveMonolingualAsJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.Job.<_worker_DoWork>b__47_0()
   at Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.5.2145</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows Server 2016 Standard</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>XXX\xxx</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>GRAFICA</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>67107792 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

- No "&" on file path

- No termbase used

- Trados versione 2019 SR2 latest update

Someone can help me?

Thank you.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hello ,

    Have you tried to open the file as a single file translation- then immediately 'SAVE TARGET AS'.

    If you have issues with the file at this stage, this will suggest there is an issue with the original source file.

    If there is no issue, then please take a look at your file settings and ensure the correct .doc (or docX0 settings are enabled.

    Trados Studio screenshot showing file type settings with a list of Microsoft Word versions and a highlighted 'doc' option.

    Lydia Simplicio | 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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 7:53 PM (GMT 0) on 28 Feb 2024]
  • 0 in reply to Lydia Simplicio

    Hi Steven,

    thank you for your kind reply.

    I solved the problem in another way; I report here the solution in case it could be useful to someone.

    First, I tried to open the file as single document and save it but, as you said, I can't generate the target file. So the problem seemed to be due to something in the original file.

    Then I...

    1. Saved the original DOC in DOCX file format
    2. Pre-translated the file with PerfectMatch
    3. Saved target file (with DOCX extension the target file was generated)

    The translated file still didn't open, but Word generated an error that could be debugged.

    With DOCX file extension the problem was in Line 2, column 72745 in "word\document.xml".

    I opened the file with 7-Zip, then I opened "document.xml" with Notepad++ and set the offset to "72745" (to open the offset window you must double click on the word "Col" in bottom-right of Notepad++ interface).

    In my case the problem was an "&" character present as metdata but not present in the "real" text.

    I simply deleted the "&" character, overwrote "document.xml" and the translated document magically opened.


    Thank you again for your support.

    Kind regards.
Reply
  • 0 in reply to Lydia Simplicio

    Hi Steven,

    thank you for your kind reply.

    I solved the problem in another way; I report here the solution in case it could be useful to someone.

    First, I tried to open the file as single document and save it but, as you said, I can't generate the target file. So the problem seemed to be due to something in the original file.

    Then I...

    1. Saved the original DOC in DOCX file format
    2. Pre-translated the file with PerfectMatch
    3. Saved target file (with DOCX extension the target file was generated)

    The translated file still didn't open, but Word generated an error that could be debugged.

    With DOCX file extension the problem was in Line 2, column 72745 in "word\document.xml".

    I opened the file with 7-Zip, then I opened "document.xml" with Notepad++ and set the offset to "72745" (to open the offset window you must double click on the word "Col" in bottom-right of Notepad++ interface).

    In my case the problem was an "&" character present as metdata but not present in the "real" text.

    I simply deleted the "&" character, overwrote "document.xml" and the translated document magically opened.


    Thank you again for your support.

    Kind regards.
Children