Term recognition window - see term details - error "Referencia a objeto no establecida como instancia de un objeto."

Hello all,

I have just upgraded from Trados 2021 to 2024 and the first thing I find is this error.

I am working with four termbases and the term recognition window shows the hits properly. However, when I want to see the details of a term, I get this error "Error dialog box in Trados Studio with a red 'X' icon, displaying a message in Spanish that translates to 'Reference to an object not set as an instance of an object.' with options for Knowledge Base and Community.
And the termbase viewer window opens and tells me there are no termbases open.

I am starting to regret upgrading.

Any help?



Generated Image Alt-Text
[edited by: RWS Community AI at 2:34 PM (GMT 1) on 12 Sep 2024]
emoji
Parents
  •  

    This message is too generic to know what might be causing this, please attach the full stack trace:

    Error dialog box in Trados Studio with a message in Spanish indicating a reference to an object not set as an instance of an object, with a tooltip suggesting to click and attach the resultant file to a reply.

    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


    Generated Image Alt-Text
    [edited by: RWS Community AI at 2:37 PM (GMT 1) on 12 Sep 2024]
  • Thank you Paul, this is the content of the file 

    <SDLErrorDetails time="12/09/2024 16:37:21">
    <ErrorMessage>Referencia a objeto no establecida como instancia de un objeto.</ErrorMessage>
    <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink/>
    <Source>Sdl.MultiTerm.Client.TerminologyProvider</Source>
    <HResult>-2147467261</HResult>
    <StackTrace>
    <![CDATA[ en Sdl.MultiTerm.Client.TerminologyProvider.TerminologyProvidersUI.MultiTermViewerWinFormsUI.GetTerminologyProviderId() en Sdl.MultiTerm.Client.TerminologyProvider.TerminologyProvidersUI.MultiTermViewerWinFormsUI.GetTermAccessLoader() en Sdl.MultiTerm.Client.TerminologyProvider.TerminologyProvidersUI.MultiTermViewerWinFormsUI.JumpToTerm(Entry entry) en Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.TerminologyProviderViewerJumpToTerm(TermHit term) ]]>
    </StackTrace>
    </Exception>
    <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.0.0.1013</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>3082</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>LAPTOP-6EMI2CSA\jicep</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>LAPTOP-6EMI2CSA</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>16586976 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>

    emoji
  •  

    Can you check the path to your termbases?  It looks as though the smaller index files are loading quickly and returning you results.  But the larger SDLTB that contains all your entries, and is the file it needs when you want to read the details, is not available so we see the NullReferenceException.  The reason I want to check the path is because if your termbase is stored in a shared drive such as OneDrive or Dropbox, then this could be the problem.

    If this is the case please try copying your termbase to a location on your computer that is not in one of these paths.  Then see if things are any better.

    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
Reply Children