Jose Ignacio Cepero Briz 

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

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>

Jose Ignacio Cepero Briz 

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.

No. My termbases are all local.

Jose Ignacio Cepero Briz 

Please share the path.  I know the termbase is on your local computer but I'd like to know what the actual path is.

Well, I thought you said the problem could be OneDrive or Dropbox, which I don't use.

But here it is: D:\Documentos\EUROPE\TBs\ERASMUS

Btw, this worked perfectly fine with Trados 2021.

Jose Ignacio Cepero Briz 

Jose Ignacio Cepero Briz said:

I thought you said the problem could be OneDrive or Dropbox, which I don't use.

They were examples, I said "shared drive such as".

Please copy the termbase to a location on your C drive and test again.

Jose Ignacio Cepero Briz said:

Btw, this worked perfectly fine with Trados 2021.

I have no doubt!!

Jose Ignacio Cepero Briz 

Also... out of interest, are you working with a MAC and this is a mapped drive by any chance?

Unfortunately C:\ERASMUS gave the same result.

I use a Windows PC.

Thank you for your efforts. I should have known better than to upgrade.

This is MUCH WORSE.

Jose Ignacio Cepero Briz 

I tried to mock up your scenario... although clearly it won't be the same as I don't have anywhere enough information from you to be able to do this eactly as you have it.  But perhaps it'll help you identify where you are doing something slightly different and perhaps spot the problem yourself.  If not I'll log a case so the support team can take a look at your problem.

Jose Ignacio Cepero Briz 

I tried to mock up your scenario... although clearly it won't be the same as I don't have anywhere enough information from you to be able to do this eactly as you have it.  But perhaps it'll help you identify where you are doing something slightly different and perhaps spot the problem yourself.  If not I'll log a case so the support team can take a look at your problem.

I've seen your video. I have the MT version you said 18.0.0.3002. One thing you said at the end "you have to make sure that they're in sync". Well, I don't know how can I do that. In principle, they should be in sync,  because I upgraded today and installed both Studio and Multiterm as downloaded. If you take a look at my last message before yours, you will see that I have the options to add terms to the termbase deactivated, grayed out, so something is definitely wrong. I am going to try repairing or reinstalling, but really I can't see what else I can dot.

Jose Ignacio Cepero Briz 

Can you show a screenshot of your termbase settings in the project settings?

Can you confirm the path to each of the termbases you have in your project.  The error message seems fairly clear in that the termbase itself is not actually there.  If we can't find the problem here then we'll get support involved.

Jose Ignacio Cepero Briz said:

I have the MT version you said 18.0.0.3002. One thing you said at the end "you have to make sure that they're in sync". Well, I don't know how can I do that.

If that's the version you have and you have 2024 (which only has one version so far) then you are in synch.