Charlotte Kauczor 

There could be several reasons for this as mentioned in this KB article:

A) The window that should display the corresponding results is not shown.
B) Either your SDL Trados Studio or your SDL MultiTerm application is not up to date.
C) There is an issue with the database index.
D) Zone Alarm (or possibly other security applications) block access to the necessary index files (*.mtf and *.mdf).

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0038785

Given you have installed 2022 it is quite possible that your security software is picking something up in this version that wasn't picked up in earlier ones.  PLease work through the suggestions in the KB and see if this helps.

A) No, the window is open.
B) Both are up to date
C) Unlikely, because 1) my colleague using the same termbase from our Groupshare (but an older Trados 2022 version) has access, 2) Terminology recognition worked properly when I used Trados 2022, version 17.0.0.11594.

D)  Unlikely, because 1) my colleague working with the same termbase has the same security settings 2) The termbase can be opened in my project settings - but the terminology is not recognized while translating 3) Terminology recognition worked properly with  Trados 2022, 17.0.0.11594. 4) I am also able to open the termbase in Multiterm.

Any other idea?

Hi Charlotte Kauczor , 

Maybe it's a stupid question, but have you tried reorganizing the termbase? This often helps when no terms are found.

Best regards

Annette (from Manfred's account)

Hi Annette,

The reorganisation button is greyed out in my version. Don't know why. I have administrator rights.
And I don't know whether it makes sense to pursue this approach, because as I mentioned:
1) Terminology recognition works for my colleague who uses the same termbase from our Groupshare server - but she uses an older Trados 2022 version), 2) Terminology recognition worked properly when I used the Trados 2022 version my colleague is still using, version 17.0.0.11594.

If you still think reorganisation makes sense, I rather need to know why the reorganisation button is greyed out.

Many thanks.

Charlotte

Hi Charlotte Kauczor ,

Maybe reorganization is not possible because another user currently has access to the underlying database. For reorganization, you need to be the only user.

Hope you can solve your problem somehow.

Best

Annette (from Manfred's account)

I have the same problem. The termbase search works, so there seems to be no problem with the termbase itself. But the term recognition windows shows no results. I can fix the problem preliminarely by starting Trados 2021 at the same time and open the same project, then close the document and open it again in Trados 2022. Hovewer, then the TM search does not work. When I close Trados 2021, the term recognition stops to work again, while the TM search goes back to normal.

All the above suggestions are not helpful. This seems to be a problem to be solved by the developers, not by the users.

The solution that will probably be proposed here, is to uninstall Trados 2021 and only work with 2022. However, the risk is far to high at this point. I use Trados daily for a living and need at least one version that is working decently. Trados 2021 still has several bugs, but works somehow. I will therefore keep this version until the most critical bugs in Trados 2022 are fixed.

I finally got help from the support who found that I have to change the way I open projects. I used to open them from the Windows Explorer. In Trados 2022, I need to switch from the Project view to the File view (double-click), set the correct language in the window on the left-hand side, and select the Open File for Translation option. Then, term recognition works. Good luck!
But you are right, there are still bugs in Trados 2022.

That's nice to hear. I always open the files from the File view. When I close Trados 2022 and start it anew, the problem is sometimes solved for a while, then starts again. It's difficult to understand why.

Charlotte Kauczor Snorre Fjeldstad 

Hi there,

I find that removing the termbase from the termbase list in the project settings, closing them then reopening and re-adding almost always solves this problem. It only happens to me in jobs that are from packages, and not very often at all.

It's all about connections not quite working as they should in that instance, and re-adding the termbase re-establishes the connection.

As Paul Filkin said above, there are many possible reasons for this scenario, which is why there are many suggestions on how to make it work better in the link that he provided.

Unfortunately it is impossible for the developers to know all the thousands of possible setups that Trados customers might be working on. Where electronic connections and communications are concerned, particularly across a network be it local or via the Cloud, there are so many external influences, other software or server behaviour for example, that can trigger problems.

Another point here is that if you want an SDL support person to take a look at your setup, you can achieve this only by starting a new thread as the SDL engineers can only set up one support case per thread.

All the best,

Ali

I have this too, it seems to be a bug that results from auto-populate. When I have a file that auto-populates segments term recognition will then stop working (although the termbase search will continue to work). The only thing that fixes this is to close and restart Trados.

The only thing more annoying than this are the current ads for Trados 2024. Fix the bugs first, please, before adding anything else!