Object reference not set to an instance of an object when validating a segment.

Once again, I am getting troubles with Trados Studio 2022 SR2 

When validating a segment, the application closes and I get that message.

I have not done any changes to my computer nor Traados Studio.

I am using Windows 11 Professionnel, 23H2.

Here is the log :

<SDLErrorDetails time="01/10/2024 22:40:41">
<ErrorMessage>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.CheckTermsWithoutTarget(ISegment source, String sourceText) 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.TranslationStudio.Editor.TranslationEditor.SingleParagraphUnitBilingualParser.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.TranslationEditor.SegmentVerifier.Verify(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode) at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.VerifySegment(ISegmentContainerNode segmentContainerNode, IParagraphUnitContainerNode paragraphContainerNode, IFileContainerNode fileContainerNode) at Sdl.TranslationStudio.Editor.TranslationEditor.SideBySideDocumentEditingView.VerifySegment() at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.ExecuteActiveSegment(SideBySideDocumentEditingView editingView, ParagraphUnitId paragraphId, SegmentId segmentId) at Sdl.TranslationStudio.Editor.TranslationEditor.Actions.AbstractConfirmSegmentAction.Execute() at Sdl.Desktop.Platform.Implementation.CommandBars.SimpleActionExecuter.Execute(ActionData actionData) at Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter`1.ExecuteWithResourceLogging(TCommandData commandData, String message) at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle) at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut) at Sdl.Platform.UI.StudioWindowForm.OnPreviewKeyDown(Keys keys) at Sdl.Platform.UI.GlobalKeysMessageFilter.PreFilterMessage(Message& m) at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified) at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at Sdl.TranslationStudio.Application.Launcher.RunApplication() ]]>
</StackTrace>
</Exception>
<Environment>
<ProductName>Trados Studio</ProductName>
<ProductVersion>Studio17</ProductVersion>
<EntryAssemblyFileVersion>17.2.11.19134</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 11 Professionnel</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1036</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>MACWIN10\PS</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>MACWIN10</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>16758060 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>



Moved error stack to code insert. Helps to avoid the spam filter!
[edited by: Paul at 9:30 PM (GMT 1) on 1 Oct 2024]
emoji
  •   

    Try turning off the term verification checks as the error is clearly coming from there.  It's these bits:

    at Sdl.Verification.TermVerifier.TermVerifierProcessing.CheckTermsWithoutTarget(ISegment source, String sourceText)
    at Sdl.Verification.TermVerifier.TermVerifierProcessing.Verify(ISegment source, ISegment target, Boolean sourceHasRevisions, Boolean targetHasRevisions)

    It could be caused by you having empty target segments or revisions in the source... it's not conclusive, but likely.  So turn it off and only run it when you're finished.

    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

    emoji