The Trados cloud platform will be undergoing maintenance on Saturday, 9th May 2026 between 05:00 to 17:00 UTC. During this time, you will not be able to log in to the Trados platform.
  • State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 429 subscribers
  • Views 1547 views
  • Users 0 members are here
Options
Related

SDL Trados Freelance 2019 : Objektverweis nicht auf eine Instanz festgelegt / NullReferenceException / Sdl.Verification.TermVerifier / Term Verifier

Christopher Köbel

Dear all,

I have recently upgraded from Trados Studio 2017 Freelance to the 2019 release and am since plagued by exception errors from the Term Verifier whenever a term is registered in MultiTerm but I chose to use another word. The error shows up when I try to Ctrl+Enter (Confirm and Go To Next Segment).

Screenshot of Trados Studio 2019 showing an exception error from the Term Verifier when confirming a segment with Ctrl+Enter.

I have read the other relevant threads here and tried various fixes proposed there, namely

  • Updating / Repairing Trados 2019 and MultiTerm
  • Renaming the %appdata%\SDL\SDL Trados Studio\15.0.0.0 folder so Trados will generate a new one
  • Reorganizing the relevant termbase(s)
  • Creating a new "Default" project and re-adding all necessary files, TMs and TBs

Yet, to no avail. Should I just wait for Trados 2021 to be downloadable for me and upgrade again, or is there a solution that will fix this annoying behaviour in 2019?
So far, I have always waited until the first service release before upgrading to a new Trados version (out of prior experience), but if this version doesn't work as expected then maybe the next will? I don't think I can go back to 2017 after having upgraded my licence...

Kind regards,
Christopher

Here's the relevant error document:

Fullscreen 20200811_SDL-Trados_Term-Verifier-Exception.sdlerror.xml Download 
<SDLErrorDetails time="11.08.2020 13:19:54">
  <ErrorMessage>Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.</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[   bei Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckForbiddenTerms(ISegment target)
   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.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.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.TranslationStudio.Editor.TranslationEditor.SingleParagraphUnitBilingualParser.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.TranslationEditor.SegmentVerifier.Verify(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.VerifySegment(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode)
   bei Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.VerifySegment()
   bei Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment()
   bei Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute()
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
   bei Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
   bei Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
   bei Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
   bei System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   bei System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
   bei System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   bei System.Windows.Forms.Control.WmKeyChar(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>15.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>15.2.7.2849</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DEFRENT\toffer</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DEFRENT</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>8326416 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Generated Image Alt-Text
[edited by: Trados AI at 10:14 PM (GMT 0) on 28 Feb 2024]
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I still had no opportunity to test this behaviour on another machine, but I have meanwhile traced it back to one particular Termbase from 2011, which apparently still has some kind of problem even after having been "Reorganized".
    I will thus try to export it and re-import the data into a new SDLTB and see if that solves the problem...

    Edit: It was, in fact, the Termbase. Apparently, an unsupported Unicode character had slipped in when copy/pasting a term. The re-import error log file warns:

    XML Parsing Error - line 1, pos 41
    Changing between current and indicated encodings is not supported.
    Wechseln zwischen aktueller und angegebener Kodierung wird nicht unterstützt.

    With the new termbase and slightly stricter import constraints than the first time I tried the export -> new SDLTB -> import routine, I have had no problems since.
Reply
  • 0

    I still had no opportunity to test this behaviour on another machine, but I have meanwhile traced it back to one particular Termbase from 2011, which apparently still has some kind of problem even after having been "Reorganized".
    I will thus try to export it and re-import the data into a new SDLTB and see if that solves the problem...

    Edit: It was, in fact, the Termbase. Apparently, an unsupported Unicode character had slipped in when copy/pasting a term. The re-import error log file warns:

    XML Parsing Error - line 1, pos 41
    Changing between current and indicated encodings is not supported.
    Wechseln zwischen aktueller und angegebener Kodierung wird nicht unterstützt.

    With the new termbase and slightly stricter import constraints than the first time I tried the export -> new SDLTB -> import routine, I have had no problems since.
Children
No Data