Customer expecting S2021 deliverables by no later than EOB today: Proofreader has delivered - one XLIFF does open correctly, the other one does not: "Ungültige Daten auf Stammebene. Zeile 284566, Position 829260"

Hi,

Customer expecting S2021 deliverables by no later than EOB today: Proofreader has delivered - one XLIFF does open correctly, the other one does not: "Ungültige Daten auf Stammebene. Zeile 284566, Position 829260" (Data at the root level is invalid. Line 284566, Position 829260).

Your help would be much appreciated. I have not found any info on the matter in the SDL Knowledge Base. An older thread on ProZ on the error message (with different figures for line and position) does not reveal what helped the original poster fix the issue.

I would prefer for someone from this forum to inspect the file (it is not super confidential) (first) rather than for me to get in touch with the proofreader right away ... The reason for that can be shared by personal message, etc. However, I am obviously OK with subsequently liaising with the proofreader, i.e. once forum participants/SDL staff have looked into the matter.

The error message file can be found below.

Cheers,

Sebastian Witte

Fullscreen sdlerror-20201012-9h45m9s.sdlerror.xml Download

<SDLErrorDetails time="12.10.2020 09:45:14">
  <ErrorMessage>Ungültige Daten auf Stammebene. Zeile 284566, Position 829260.</ErrorMessage>
  <Exception>
    <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <LineNumber>284566</LineNumber>
    <LinePosition>829260</LinePosition>
    <SourceUri />
    <HelpLink />
    <Source>System.Xml</Source>
    <HResult>-2146232000</HResult>
    <StackTrace><![CDATA[   bei System.Xml.XmlTextReaderImpl.Throw(Exception e)
   bei System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   bei System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   bei System.Xml.XmlTextReaderImpl.Read()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.WhitespacePreservingXmlTextReader.Read()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning()
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.GenericStreamReader.ProcessInternalStream(Stream stream)
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.GenericStreamReader.ProcessStream(String xliffInputFilePath, String encryptionKey)
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.InitializeDocumentProperties(String encryptionKey)
   bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.BeginParsing()
   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.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile)
   bei Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>Studio16</ProductVersion>
    <EntryAssemblyFileVersion>16.0.2.3343</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-M263836\Nutzer</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-M263836</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>33504084 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Customer expecting S2021 deliverables by no later than EOB today: Proofreader has delivered - one XLIFF does open correctly, the other one does not: "Ungültige Daten auf Stammebene. Zeile 284566, Position 829260" Hi, Customer expecting S2021 deliverables by no later than EOB today: Proofreader has delivered - one XLIFF does open correctly, the other one does not: "Ungültige Daten auf Stammebene. Zeile 284566, Position 829260" (Data at the root level is invalid. Line 284566, Position 829260). Your help would be much appreciated. I have not found any info on the matter in the SDL Knowledge Base. An older thread on ProZ on the error message (with different figures for line and position) does not reveal what helped the original poster fix the issue. I would prefer for someone from this forum to inspect the file (it is not super confidential) (first) rather than for me to get in touch with the proofreader right away ... The reason for that can be shared by personal message, etc. However, I am obviously OK with subsequently liaising with the proofreader, i.e. once forum participants/SDL staff have looked into the matter. The error message file can be found below. Cheers, Sebastian Witte .code-editor .code-editor-heading{border-top:1px solid #eaeaeb;border-left:1px solid #eaeaeb;border-right:1px solid #eaeaeb;background-color:#fbfbfb;border-radius:3px 3px 0 0;font-size:12.6px;display:flex;justify-content:space-between;align-items:center;overflow:hidden}.code-editor .code-editor-heading .icon{width:32px;height:32px;display:block;overflow:hidden;text-indent:-3000em;background-repeat:no-repeat;background-size:80%;background-position:center}.code-editor .code-editor-heading .fs{background-image:url('https://community.rws.com/cfs-filesystemfile/__key/defaultwidgets/547b4cbb4efb4c3d83533f8f35fb4b7b-1a84591e31034fac832d29ed8584666c/fullscreen.svg?_=637923381702208350')}.code-editor .code-editor-heading .dl{background-image:url('https://community.rws.com/cfs-filesystemfile/__key/defaultwidgets/547b4cbb4efb4c3d83533f8f35fb4b7b-1a84591e31034fac832d29ed8584666c/download.svg?_=637923381702118315')}.code-editor .code-editor-heading .filename{padding:10px;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.code-editor .code-editor-heading a{color:#3e414a}.code-editor .code-editor-heading a:hover{color:teal} https://community.rws.com/# https://community.rws.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/90/sdlerror_2D00_20201012_2D00_9h45m9s.sdlerror.xml?_=637380869199959696 https://community.rws.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/90/sdlerror_2D00_20201012_2D00_9h45m9s.sdlerror.xml?_=637380869199959696 <SDLErrorDetails time="12.10.2020 09:45:14"> <ErrorMessage>Ungültige Daten auf Stammebene. Zeile 284566, Position 829260.</ErrorMessage> <Exception> <Type>System.Xml.XmlException, System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type> <LineNumber>284566</LineNumber> <LinePosition>829260</LinePosition> <SourceUri /> <HelpLink /> <Source>System.Xml</Source> <HResult>-2146232000</HResult> <StackTrace><![CDATA[ bei System.Xml.XmlTextReaderImpl.Throw(Exception e) bei System.Xml.XmlTextReaderImpl.Throw(String res, String arg) bei System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() bei System.Xml.XmlTextReaderImpl.ParseDocumentContent() bei System.Xml.XmlTextReaderImpl.Read() bei Sdl.FileTypeSupport.Bilingual.SdlXliff.WhitespacePreservingXmlTextReader.Read() bei Sdl.FileTypeSupport.Bilingual.SdlXliff.SdlXliffFeeder.ContinueScanning() bei Sdl.FileTypeSupport.Bilingual.SdlXliff.GenericStreamReader.ProcessInternalStream(Stream stream) bei Sdl.FileTypeSupport.Bilingual.SdlXliff.GenericStreamReader.ProcessStream(String xliffInputFilePath, String encryptionKey) bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.InitializeDocumentProperties(String encryptionKey) bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileReader.BeginParsing() 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.Conversion.ConversionTask.ProcessFile(IExecutingTaskFile executingTaskFile) bei Sdl.ProjectApi.AutomaticTasks.AbstractFileLevelAutomaticTaskImplementation.Execute()]]></StackTrace> </Exception> <Environment> <ProductName>SDL Trados Studio</ProductName> <ProductVersion>Studio16</ProductVersion> <EntryAssemblyFileVersion>16.0.2.3343</EntryAssemblyFileVersion> <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem> <ServicePack>NULL</ServicePack> <OperatingSystemLanguage>1031</OperatingSystemLanguage> <CodePage>1252</CodePage> <LoggedOnUser>DESKTOP-M263836\Nutzer</LoggedOnUser> <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork> <ComputerName>DESKTOP-M263836</ComputerName> <ConnectedToNetwork>True</ConnectedToNetwork> <PhysicalMemory>33504084 MB</PhysicalMemory> </Environment> </SDLErrorDetails> jQuery(function(j){ var fullScreenToggle = j('#fragment-1a84591e31034fac832d29ed8584666c1367545539_code-editor-fs'); var codeEditor = j('#fragment-1a84591e31034fac832d29ed8584666c1367545539_code-editor'); fullScreenToggle.on('click', function(){ if (codeEditor.evolutionCodeEditor('fullscreen')) { codeEditor.evolutionCodeEditor('fullscreen', false); } else { codeEditor.evolutionCodeEditor('fullscreen', true); } return false; }); });
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Top Replies

Astrid Elke Witte over 5 years ago +1 verified

Fixed by SDL Support within the context of a support ticket. They wrote: "The problem was caused by a <trans-unit> element (and all of its child elements) added at the end of the file. From a structural…

Parents

+1 Astrid Elke Witte over 5 years ago

Fixed by SDL Support within the context of a support ticket. They wrote:

"The problem was caused by a <trans-unit> element (and all of its child elements) added at the end of the file. From a structural perspective, this caused a “nesting” issue which rendered the .sdlxliff invalid.

Unfortunately, there are still two “unknowns” here:

- It is impossible to determine what caused this data corruption. I usually see this happening when the .sdlxliff is stored on a network location (Google Drive, Dropbox, etc. …) and accessed in Studio from there."

Documentation Survey: help us offer you better documentation! Translate

Reply

+1 Astrid Elke Witte over 5 years ago

Fixed by SDL Support within the context of a support ticket. They wrote:

"The problem was caused by a <trans-unit> element (and all of its child elements) added at the end of the file. From a structural perspective, this caused a “nesting” issue which rendered the .sdlxliff invalid.

Unfortunately, there are still two “unknowns” here:

- It is impossible to determine what caused this data corruption. I usually see this happening when the .sdlxliff is stored on a network location (Google Drive, Dropbox, etc. …) and accessed in Studio from there."

Documentation Survey: help us offer you better documentation! Translate

Children

No Data

Trados Studio > 1. Trados Studio

Customer expecting S2021 deliverables by no later than EOB today: Proofreader has delivered - one XLIFF does open correctly, the other one does not: "Ungültige Daten auf Stammebene. Zeile 284566, Position 829260"

Top Replies