• State Verified Answer
  • Replies 9 replies
  • Subscribers 432 subscribers
  • Views 569 views
  • Users 0 members are here
Options
Related

"Object reference not set to an instance of an object" - yes, THAT age-old problem again!

Alain Alameddine

I face this issue on an updated registered version of Trados 2019 as well as an updated trial version of Trados 2021. If I try to use an existing termbase, adding a term to it leads to the same. I tried to google it but solutions there didn't do the trick.

Error log:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<SDLErrorDetails time="1/19/2024 6:10:51 AM">
<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.MultiTerm.Core.Common</Source>
<HResult>-2147467261</HResult>
<StackTrace>
<![CDATA[ at Sdl.MultiTerm.Core.Common.DataContainers.TermbaseStatus..ctor(ITermbaseInfo info) at Sdl.MultiTerm.Client.MiniEditor.MiniEditorControl..ctor(ITermbaseInfo activeTermbase, ITermHit activeTerm) at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(ITermbaseInfo termbaseInfo, String source, String target) at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(String source, String target) at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.TerminologyProviderViewerAddTerm(String source, String target) at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.AddTerm(ITerminologyProvider termbase, String source, String target) at Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseUtils.AddTerm(IEditorService editorService, ITranslatableDocument translatableDocument, String sourceText, String targetText) at Sdl.TranslationStudio.Editor.Terminology.Actions.AbstractAddNewTermAction.AddTerm() at Sdl.TranslationStudio.Editor.Terminology.Actions.QuickAddNewTerm.Execute() at Sdl.Desktop.Platform.Implementation.CommandBars.StaticAction.Execute() at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0() at Sdl.Desktop.Logger.Log.Resources(Object message, Action action) at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle) at Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute() at Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e) at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e) at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e) at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e) at Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick() at Infragistics.Win.UltraWinToolbars.ToolMenuItem.OnClick() at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.DoClickProcessing(MouseEventArgs e) at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.OnMouseUp(MouseEventArgs e) at Infragistics.Win.TextUIElementBase.OnMouseUp(MouseEventArgs e) at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e) at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e) at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e) at Infragistics.Win.UltraWinToolbars.PopupControlBase.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at 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.8.3007</EntryAssemblyFileVersion>
<OperatingSystem>Microsoft Windows 11 Home</OperatingSystem>
<ServicePack>NULL</ServicePack>
<OperatingSystemLanguage>1033</OperatingSystemLanguage>
<CodePage>1252</CodePage>
<LoggedOnUser>ENVY\alain</LoggedOnUser>
<DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
<ComputerName>ENVY</ComputerName>
<ConnectedToNetwork>True</ConnectedToNetwork>
<PhysicalMemory>16539192 MB</PhysicalMemory>
</Environment>
</SDLErrorDetails>
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Alain Alameddine

     

    The stack trace shows that the exception is thrown during the construction of a TermbaseStatus object, which fails because it receives a null ITermbaseInfo parameter. This indicates that the operation fails to reference an existing term base correctly, either because the term base is not loaded, is inaccessible, or the reference to the term base is lost during the operation.

    Can you check whether you are using OneDrive or something similar for your Termbases.  This sort of problem is exactly what I would expect if your termbases are in the cloud and not set to be available locally.  Studio will be able to see the name as that's what OneDrive does, but the termbase itself will not be accessible for 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

    emoji
Children