Hello Ignacio Niveiro ,

Thank you for the information provided- there seems to be a number of sources which might be causing the issues.

First of all I would suggest running through the following articles (1&2) to make sure everything is really up to date.

community.sdl.com/.../3392.how-to-part-1-trouble-shoot-unexplained-errors-and-unwanted-behavior-in-studiomultiterm

Now in reference to the error message -This does appear to suggest that the corrupt entry/entries are indeed part of the problem.- 

Unknown said:

StackTrace><![CDATA[   at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckTermsWithoutTarget(ISegment source, String sourceText)

So maybe (and to eliminate this error source first of all) remove the Termbase from the project, open your Termbase and correct the broken term you already know is broken. Simply reorganising the Termbase wont necessarily fix such issues.

Unknown said:

Apparently one term in my termbase is ALSO broken (don't think it was responsable for the slow processing, though.. it's just and additional problem!)

Now add the TB back into the project and see if the issues have been resolved and the error is no longer appearing.

Hi, Paul ,

is there already a solution for this? We keep getting a similar error with Check Forbidden Terms (see Stacktrace). We have the latest Trados Studio 2022 version (including SR1 and CU1): 17.1.8.17828

<SDLErrorDetails time="24.10.2023 15:18:32">
  <ErrorMessage>Failed to verify document: Object reference not set to an instance of an object.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.Verification.TermVerifier</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   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.8.17828</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>MEWO\skat</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>PC-AT11-008</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8274236 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Katharina Schuhmann 

Katharina Schuhmann said:

is there already a solution for this?

No.

Only solution is normally to disable term verification.  I think you'll need to wait for the next major release before this gets resolved as there are some pretty wide ranging changes expected which should allow us to start improving the terminology experience in Studio.

 Paul 

This is unfortunate, but okay... :( Do you know when the next major release will be?

Katharina Schuhmann 

Katharina Schuhmann said:

Do you know when the next major release will be?

No.  We haven't published any details on this yet.

Paul Okay, thanks for your help anyway. :)