Studio 2022; error message 'Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index'

When I launch the QA controls on the file I'm working on with F8, I get this message. and the QA checks are interrupted
I am working on a package received from a client, which includes a Termbase. If I deactivate the Termbase from the project settings, the error disappears and QA checks are completed correctly.
Verification settings include terminology checks. If I do not remove the termbase but disable terminology checks, QA is carried out correctly.
I am running Trados Studio 2022 SR1 - 17.1.6.16252, Multiterm 2022 SR1 - 17.1.1.2185, and Windows 11 duly updated.

I attach the error stack:

Fullscreen 3618.sdlerror-2023714-13h44m7s.sdlerror.sdlerror.xml Download

<SDLErrorDetails time="14/07/2023 13:51:55">
  <ErrorMessage>Failed to verify document: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index</ErrorMessage>
  <Exception>
    <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ParamName>index</ParamName>
    <HelpLink />
    <Source>mscorlib</Source>
    <HResult>-2146233086</HResult>
    <StackTrace><![CDATA[   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at Sdl.Verification.TermVerifier.TermVerifierProcessing.HasAnyForbiddenFields(ISegment target, Boolean found, ITermRecognitionHit hit, IEntryTerm term)
   at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckForbiddenTerms(ISegment target)
   at Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(ISegment source, ISegment target, Boolean sourceHasRevisions, Boolean targetHasRevisions)
   at Sdl.Verification.TermVerifier.TermVerifierMain.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit)
   at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkParagraphContainerField* field)
   at FrameworkParagraphContainerField.vv_AcceptFrameworkVisitor(FrameworkParagraphContainerField* , 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.Verification.VerifyDocumentJobRequest.PerformBilingualVerification()
   at Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.Execute(IJobExecutionContext context)
   at Sdl.Desktop.Platform.Implementation.Services.JobExecuter.Execute(JobData jobData)
   at Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message)
   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>Trados Studio</ProductName>
    <ProductVersion>Studio17</ProductVersion>
    <EntryAssemblyFileVersion>17.1.6.16252</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1040</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-K15369G\FDL</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-K15369G</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>33255512 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Thanks for your help.

Kind regards

Fulvio Giglio

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Studio 2022; error message 'Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index' When I launch the QA controls on the file I'm working on with F8, I get this message. and the QA checks are interrupted I am working on a package received from a client, which includes a Termbase. If I deactivate the Termbase from the project settings, the error disappears and QA checks are completed correctly. Verification settings include terminology checks. If I do not remove the termbase but disable terminology checks, QA is carried out correctly. I am running Trados Studio 2022 SR1 - 17.1.6.16252, Multiterm 2022 SR1 - 17.1.1.2185, and Windows 11 duly updated. I attach the error stack: .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/3618.sdlerror_2D00_2023714_2D00_13h44m7s.sdlerror.sdlerror.xml?_=638249680383565728 https://community.rws.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/90/3618.sdlerror_2D00_2023714_2D00_13h44m7s.sdlerror.sdlerror.xml?_=638249680383565728 <SDLErrorDetails time="14/07/2023 13:51:55"> <ErrorMessage>Failed to verify document: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index</ErrorMessage> <Exception> <Type>System.ArgumentOutOfRangeException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type> <ParamName>index</ParamName> <HelpLink /> <Source>mscorlib</Source> <HResult>-2146233086</HResult> <StackTrace><![CDATA[ at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource) at Sdl.Verification.TermVerifier.TermVerifierProcessing.HasAnyForbiddenFields(ISegment target, Boolean found, ITermRecognitionHit hit, IEntryTerm term) at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckForbiddenTerms(ISegment target) at Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(ISegment source, ISegment target, Boolean sourceHasRevisions, Boolean targetHasRevisions) at Sdl.Verification.TermVerifier.TermVerifierMain.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.LocationMarkerLocator.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Framework.Integration.FileExtractor.ProcessParagraphUnit(IParagraphUnit paragraphUnit) at Sdl.FileTypeSupport.Bilingual.Tmfc.TmfcReaderImpl.vv_Visit(TmfcReaderImpl* , FrameworkParagraphContainerField* field) at FrameworkParagraphContainerField.vv_AcceptFrameworkVisitor(FrameworkParagraphContainerField* , 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.Verification.VerifyDocumentJobRequest.PerformBilingualVerification() at Sdl.TranslationStudio.Editor.Verification.VerifyDocumentJobRequest.Execute(IJobExecutionContext context) at Sdl.Desktop.Platform.Implementation.Services.JobExecuter.Execute(JobData jobData) at Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message) 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>Trados Studio</ProductName> <ProductVersion>Studio17</ProductVersion> <EntryAssemblyFileVersion>17.1.6.16252</EntryAssemblyFileVersion> <OperatingSystem>Microsoft Windows 11 Pro</OperatingSystem> <ServicePack>NULL</ServicePack> <OperatingSystemLanguage>1040</OperatingSystemLanguage> <CodePage>1252</CodePage> <LoggedOnUser>DESKTOP-K15369G\FDL</LoggedOnUser> <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork> <ComputerName>DESKTOP-K15369G</ComputerName> <ConnectedToNetwork>True</ConnectedToNetwork> <PhysicalMemory>33255512 MB</PhysicalMemory> </Environment> </SDLErrorDetails> jQuery(function(j){ var fullScreenToggle = j('#fragment-1a84591e31034fac832d29ed8584666c1162346731_code-editor-fs'); var codeEditor = j('#fragment-1a84591e31034fac832d29ed8584666c1162346731_code-editor'); fullScreenToggle.on('click', function(){ if (codeEditor.evolutionCodeEditor('fullscreen')) { codeEditor.evolutionCodeEditor('fullscreen', false); } else { codeEditor.evolutionCodeEditor('fullscreen', true); } return false; }); }); Thanks for your help. Kind regards Fulvio Giglio
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Top Replies

Paul over 1 year ago +1 verified

Fulvio Giglio Thanks for providing these details. By looking at the stack trace, it looks as though the problem may be coming from the method "HasAnyForbiddenFields" in the class "TermVerifierProcessing…

Parents

+1 Paul over 1 year ago
Fulvio Giglio

Thanks for providing these details. By looking at the stack trace, it looks as though the problem may be coming from the method "HasAnyForbiddenFields" in the class "TermVerifierProcessing",,, maybe this:

CheckForbiddenTerms receives a target segment as an argument.

This function then calls HasAnyForbiddenFields, passing the target segment along with other parameters.

Within HasAnyForbiddenFields, the function attempts to access an element in a collection at a specific index.

However, the specified index is larger than the number of elements in the collection (i.e., it's out of range), resulting in an ArgumentOutOfRangeException.

Can you share the settings you are using here?

Maybe also try changing your settings so you don't check for forbidden terms? Just as a test... clearly it should always work, and preferably should not throw an error even if your termbase has a problem. If possible can you share your termbase? Or maybe a screenshot of your termbase definition if your termbase cannot be shared?

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
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Paul

You are right, Paul.
The problem was indeed the forbidden terms check, which was selected but with no actual forbidden terms list.
I deselected it and now it's all good.

Thanks so much!
Kind regards
F
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Fulvio Giglio

... ands sorry for the "sentiment" label... there's no hard feelings as far as I'm concerned ;-)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 1 year ago in reply to Fulvio Giglio

Fulvio Giglio

Always tricky getting the sentiment right... I often check and then can't bring myself to use the suggested language. For example:

"Absolutely! I've successfully saved the termbase's definition in an xdt file. Will this work well for our needs?"

It's a great score and very happy... but sticks in my throat a little ;-)

Fulvio Giglio said:
xdt file... would that do?

Absolutley ;-) You'll probably have to zip it to get it in the forum when you attach 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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Paul

I'm with you. I tend to be very concise.

Nevertheless, it is with pleasure that I am attaching the required file, with the hope of it being helpful in the quest for a solution. ;-)

Definition for XXXXXX Master Termbase for Paul RWS.zip

Kind regards Paul, and thanks for all your efforts.
F
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 1 year ago in reply to Fulvio Giglio

Thanks Fulvio Giglio

Will test shortly.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 1 year ago in reply to Paul

Fulvio Giglio

ok... not the result I was hoping for on using F8:

In my settings I have this with no forbidden values selected:

Can you confirm what settings you have here?

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Paul

Here it comes, Paul.
After I deselected the "Check for terms which may have been set as forbidden" checkbox, the problem was solved, but the "Forbidden" checkbox in the "Select forbidden value" stayed selected and I could not deselect it (and still can't).

I hope this helps
Kind regards

F

Generated Image Alt-Text
[edited by: Trados AI at 11:43 AM (GMT 0) on 29 Feb 2024]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 1 year ago in reply to Fulvio Giglio

Thanks Fulvio Giglio

No... I still can't repro. I have the same settings as you now:

If you can't deselect this could be related to it being a package with controls over that. So I'll create a package and see if someone can reproduce with a protected package I create from these settings.

Thank you for spending time trying to help reproduce it. It can be really tricky sometimes and when we can't repro it's similarly hard to fix!

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Paul

Good luck!

TIll next time
Kind regards
F
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 1 year ago in reply to Fulvio Giglio

Fulvio Giglio

This has now been reproduced and raised as our reference CRQ-34819 (for ease of finding later). It seems that the term check will find forbidden terms even if it should not do and it's most likely related to the changes made for SR1:

"Enhanced terminology handling with reduced false positives in the term check"

So far, we can only suggest disabling the Forbidden Terms check which is the solution you have already found. But hopefully we can now plan the work in and resolve 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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Fulvio Giglio over 1 year ago in reply to Paul

Thanks for keeping me posted.

KInd regards
F
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate