"Probability score": 0.8

"Question improvement suggestion": Please provide more details about the steps you took before encountering the error, and any recent changes to your system or software. Also, if there are any error codes accompanying the error message, please include them.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Laura,

I'm sorry to hear that you're experiencing issues with Trados Studio 2022 SR2 - 17.2.11.19134. The error message you're seeing, "Object reference not set to an instance of an object," is a common one in programming and typically means that an object is being used that hasn't been initialized or is currently null.

Here's a workaround that might help:

Step 1: Open your project in Trados Studio.

Step 2: Navigate to the termbase where you're trying to add a new term.

Step 3: Click on any of the existing terms in the termbase.

Step 4: Try again to add the new term.

This issue has been logged with our Development team, and they are working on a permanent fix. In the meantime, this workaround should allow you to continue your work.

As for the Term Recognition function not working, it could be due to a number of reasons. Here are a few troubleshooting steps:

Step 1: Check if the correct termbase is loaded in your project settings.

Step 2: Make sure the language direction in your termbase matches the language direction of your project.

Step 3: Try to search for the term directly in the termbase to see if it exists.

If these steps don't resolve your issue, please provide more details about the problem, and we'll be happy to assist further.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

I followed instructions and after having checked that all the requirements are ok, I tried to open the termbase but I got the following erroe message:

Can you please explain what's going on? Yesterday the search into the termbases from Studio worked perfectly.

Thanks in advance. 

Laura Bigi 

I suggest you try the steps described in this KB article:
MultiTerm does not open after Windows 11 installation\upgrade and gives the " Unable to cast COM object of type 'Sdl.Multiterm.TMO.Interop.TermbaseRepositoryClass' " error message.

That's it! Yesterday company settings arranged for the Windows 11 upgrade....after that the problem with MultiTerm arose...

Do you know if the upgrade problem will be fixed from RWS? Otherwise how can I use MultiTerm if company already made the Windows 11 upgrade mandatory?

I am waiting for Studio 2024 installation....the above problem is not fixed also for it?

Thanks a lot for your reply.

Laura Bigi 

Laura Bigi said:

I am waiting for Studio 2024 installation....the above problem is not fixed also for it?

I run 2024 on my personal laptop (W11) and don't have this problem... so I would say the problem is fixed.  I did notice something odd in that I created the termbase via Studio and when I added the first couple of terms all I saw was a "no open termbase" message.  So I closed the project and reopened, and the terms had actually been added... and the termbase behaved perfectly thereafter.  So a bit odd, and I'm not sure why, but it seems to work ok.

Laura Bigi 

Laura Bigi said:

I am waiting for Studio 2024 installation....the above problem is not fixed also for it?

I run 2024 on my personal laptop (W11) and don't have this problem... so I would say the problem is fixed.  I did notice something odd in that I created the termbase via Studio and when I added the first couple of terms all I saw was a "no open termbase" message.  So I closed the project and reopened, and the terms had actually been added... and the termbase behaved perfectly thereafter.  So a bit odd, and I'm not sure why, but it seems to work ok.