Hallo Community,
nach der Qualitätsprüfung habe ich folgende Fehlermeldung erhalten und konnte die Prüfung nicht abschließen: "Das Dokument konnte nicht geprüft werden: Der Index und die Länge müssen sich auf eine Position in der Zeichenfolge beziehen."
Weiß jemand dafür eine Lösung?
Vielen Dank vorab
.
What is your file type? Do you have any embedded content in it? Also, posting the full stack trace message error may help:
Kind regards,
Elisa Maxim | 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
Hi Elisa, the project contains .txt files. I figured out that this error only occurs when attemting to do the terminology check. The usual QA check works fine and I can go through all errors. Hoewever, terminoogy errors won't be shown. Do you know why this error message occurs? Thank you in advance. Beneath the full stack trace message:
This XML file does not appear to have any style information associated with it. The document tree is shown below. <SDLErrorDetails time="14.11.2024 12:56:18"> <ErrorMessage>Das Dokument konnte nicht geprüft werden: Der Index und die Länge müssen sich auf eine Position in der Zeichenfolge beziehen. Parametername: length</ErrorMessage> <Exception> <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type> <ParamName>length</ParamName> <HelpLink/> <Source>mscorlib</Source> <HResult>-2146233086</HResult> <StackTrace> <![CDATA[ bei System.String.Substring(Int32 startIndex, Int32 length) bei Sdl.MultiTerm.Core.XmlProcessor.EntryXmlProcessor.Transform(String inputXml) bei Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(MultiTermTermbase termbase, Int32 id) bei Sdl.MultiTerm.Client.TerminologyProvider.MultiTermTermbase.GetEntry(Int32 id) bei Sdl.MultiTerm.Client.TerminologyProvider.TerminologyPrioviders.AbstractMultiTermTerminologyProvider.GetEntry(Int32 id) bei Sdl.MultiTerm.Client.TerminologySearch.TermRecognitionHit.get_Entry() bei Sdl.Verification.TermVerifier.TermVerifierProcessing.HasTargetEntry(ITermRecognitionHit sourceHit) bei Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckTermUsage() bei Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(ISegment Source, ISegment Target, Boolean sourceHasRevisions, Boolean targetHasRevisions) bei Sdl.Verification.TermVerifier.TermVerifierMain.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) bei Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkParagraphContainerField* field) bei FrameworkParagraphContainerField.vv_AcceptFrameworkVisitor(FrameworkParagraphContainerField* , FrameworkFieldVisitor* visitor) bei Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_VisitStartEndField(TmfcReaderImpl* , StartEndField* startEnd) bei Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.b_VisitNext(TmfcReaderImpl* ) bei Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReader.ParseNext() bei Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ParseNext() bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext() bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse() bei Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.PerformBilingualVerification() bei Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.Execute(IJobExecutionContext context) bei Sdl.Desktop.Platform.Implementation.Services.JobExecuter.Execute(JobData jobData) bei Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message) bei Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e) bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) ]]> </StackTrace> </Exception> <Environment> <ProductName>Trados Studio</ProductName> <ProductVersion>Studio16</ProductVersion> <EntryAssemblyFileVersion>16.2.12.9338</EntryAssemblyFileVersion> <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem> <ServicePack>NULL</ServicePack> <OperatingSystemLanguage>1031</OperatingSystemLanguage> <CodePage>1252</CodePage> <LoggedOnUser>PROVERB-STGT\adriana.mosch</LoggedOnUser> <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork> <ComputerName>VMOSCH</ComputerName> <ConnectedToNetwork>True</ConnectedToNetwork> <PhysicalMemory>8387528 MB</PhysicalMemory> </Environment> </SDLErrorDetails>
The forum reply was determined to be SPAM (by 'Text Repetition'). The author responded on 14 Nov 2024 1:04 PM. Author's Response I was asked to show the full error message and copied it into my answer so the community can maybe better understand where the problem with this error message lies.
I approved your post. The reason it's picked up as spam is because you pasted the message in as text. To avoid this please insert it as code or even easier just attach the file you save to your desktop.
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
On the error. It is indeed related to the verification. I think, given the age of your software, the solution is to not run the verification check for terminology. So just uncheck that from your verification options.
It might be caused by something in the specific termbase, and it might be the result of a bug, but even if we found it there wouldn't be a fix for that version of the product I'm afraid.
If you can validate this in the current version that would be worth a look? If you have time you could download the trial and test it?
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
On the error. It is indeed related to the verification. I think, given the age of your software, the solution is to not run the verification check for terminology. So just uncheck that from your verification options.
It might be caused by something in the specific termbase, and it might be the result of a bug, but even if we found it there wouldn't be a fix for that version of the product I'm afraid.
If you can validate this in the current version that would be worth a look? If you have time you could download the trial and test it?
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
Thank you for your explanations, Paul. The error also occurs when using the latest version of Trados, 2024. I tested both versions of Trados.
The terminology check is crucial for this project. I have solved the problem by opening only 2 to 3 files (instead of 10) and the terminology check worked. It's still not the final solution for this error message but at least the I can run the terminology check.
Translate
