• State Verified Answer
  • Replies 1 reply
  • Subscribers 189 subscribers
  • Views 55 views
  • Users 0 members are here
Options
Related

Object reference errors due to corrupt terms in server termbase

Katharina Schuhmann

Hi,

We have not had this problem for a long while, but it seems that the last termbase reorganisation we did created some serious problems in our MultiTerm server termbase. Some terms are now 'corrupt', i.e. they cannot be searched for and produce this error:

Error message dialog with title 'Fehler' and text 'The entry number does not exist in this termbase.' with an OK button.

However, I see them in the term list under 'Durchsuchen': the first 'Werkzeug' is normal, the last one, too, the two in the middle are corrupt. They can neither be copied nor exported nor deleted.

List of terms with four entries labeled 'Werkzeug', where the second entry is highlighted.

The worst problem of all is that these corrupt terms make Studio crash when confirming a segment with these terms. You hit Crtl+Enter and whoop! Studio is gone. No error message.

An error message does appear when hitting F8 for the verification:

Fullscreen Verification error due to corrupt terms.sdlerror.xml Download 
<SDLErrorDetails time="15.07.2025 08:14:23">
  <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.HasTargetEntry(TermRecognitionHit sourceHit, List`1 targetTermsNotMatched)
   at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckTermUsage()
   at Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(IMessagingHelper messagingHelper, ISegment source, ISegment target)
   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>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.0.2.3255</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Enterprise</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>MEWO\skat</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>NB-AT11-203</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16489528 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

The last time we had corrupt terms we ended up needing a lengthy support session with RWS, but I'll post this here anyway because the behaviour is slightly different than last time and I'm hoping for a swifter answer. Any help is appreciated!

Best regards,
Katharina

Studio version: Trados Studio 2024 - 18.0.2.3255

MultiTerm version: Multiterm 2024 - 18.0.2.3266

Generated Image Alt-Text
[edited by: RWS Community AI at 6:19 AM (GMT 1) on 15 Jul 2025]
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Probability score: 0.8  

    Question improvement suggestion: Provide specific details about any troubleshooting steps you have already taken to resolve the issue, such as attempts to reorganize the termbase or any error messages encountered.  

    In the meantime, based on the information you have provided, here is a suggested answer to your question:  

    Hello Katharina,  

    It sounds like you're experiencing significant issues with your MultiTerm server termbase due to corrupt terms, which is understandably frustrating. Here’s a step-by-step approach to help you resolve this issue:  

    **Step 1:** **Recreate the Termbase**  

    - Open MultiTerm Desktop.  

    - Create a new termbase with the same structure as your existing one by selecting 'Create Termbase...' and following the wizard.  

    - This process will typically discard corrupted entries, so you will need to re-add any necessary terms afterward.  

    **Step 2:** **Export and Import Data**  

    - If you have a backup of your termbase data, export it.  

    - Import this data into the newly created termbase. Make sure to select the option for Fast Import if your data is compliant with MultiTerm XML.  

    **Step 3:** **Check for Updates**  

    - Ensure that both Trados Studio and MultiTerm are updated to the latest versions. This can help resolve compatibility issues that may be causing the crashes.  

    **Step 4:** **Verify Document Settings**  

    - Before running the verification, try unchecking all the checkboxes in the Verification options and then check them one at a time to identify if a specific setting is causing the crash.  

    **Step 5:** **Monitor for Errors**  

    - After following these steps, monitor for any error messages or crashes when confirming segments. If the issue persists, consider documenting any specific error messages that appear for further troubleshooting.  

    If these steps do not resolve the issue, you may need to consider reaching out for more specialized support. I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

    RWS Community AI
    emoji