Term recognition not working in Trados Studio 2022

Question

I am using Trados 2022 Version 17.0.2.11672 and the term recognition is not working in Trados Studio. 
 The termbase is set correctly in the project settings but the term recognition window says that no termbase is opened and does not show any matches. 
 It worked properly with my first Trados 2022 Version 17.0.0.11594 (and with Trados 2021 and Trados 2019). 
 The termbase is located on our server. My colleague who still uses the older version (17.0.0.11594) has no issues with the use of the same termbase. 
 Removing and reopening of the termbase does not help. 
 An issue with the latest release? 
 Or any other suggestions?

Charlotte Kauczor · Accepted Answer

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?

Paul Filkin · Answer

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.

Alison Field · Answer

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

Alison Field · Answer

Edward Bradburn Charlotte Kauczor Snorre Fjeldstad Manfred Altmann 
 Hi Edward, 
 Have you tried removing the termbase/s from the termbase list in the project settings, closing Studio, then reopening and re-adding the termbase/s? 
 Or the solution here No results... suggested by Paul Filkin ? Or the workaround that worked for Charlotte Kauczor above? 
 If none of the solutions suggested above worked for you, can I suggest that you open a NEW thread and explain in as much detail as possible what is happening to cause your problem. Include details of which version of both Studio and MultiTerm you are using (they need to be the right version for each other) and what steps cause the issue to arise. 
 That way, Trados support can contact you (they can only trigger one case per thread) and, if you like, take a look at your setup and hopefully resolve your problem. 
 Here's how: Click the +New button top right of your screen to create a new thread, ask your question again and someone will contact you from RWS Support.

All the best, 
 Ali 
 PS: If you'd like to learn more about this or any other aspect of using Trados, you can ask for free training by going here: 
 Ideas for training 
 Please take a look and add a new post explaining what you would like to learn, including details that will help so that others will want to vote for your idea!

Alison Field · Answer

Edward Bradburn said: The only thing that fixes this is to close and restart Trados. 
 I apologise, you've already said that my suggestion works... I was too quick to reply without reading what you actually wrote. My bad! I was also posting for the benefit of everyone else who had this problem... 
 If you want to find a more permanent solution, please do start a new thread as I described in my post. 
 All the best, 
 Ali

Trados Studio > 3. MultiTerm

Term recognition not working in Trados Studio 2022

Top Replies