The "Repair" did not fix the issue. Reinstalling "SDL Multiterm 2017" after "removing suite of products" did the trick.
By the way, initially I was thinking that I could repair this issue just by going either to the Ribbon or the Options section of Studio and find if the link was errouneosly pointing to the Multiterm 12 folder (ie, Multiterm 2015) instead of the Multiterm 14 folder (ie, Multiterm 2017) and correct that. I could not find that information and I believe it would be nice to have that feature somewhere in Options. In addition, I also thought I could go somewhere and just manually edit some XML configuration file, as a quick and dirt solution in the absence of a feature within Options.

Unknown said:

By the way, initially I was thinking that I could repair this issue just by going either to the Ribbon or the Options section of Studio and find if the link was errouneosly pointing to the Multiterm 12 folder (ie, Multiterm 2015) instead of the Multiterm 14 folder (ie, Multiterm 2017) and correct that. I could not find that information and I believe it would be nice to have that feature somewhere in Options.

Hello Ozzie,

Probably not a good idea.  You really need to make sure that MultiTerm is always updated to work with the version of Studio you have.  The situation you were in is unusual and often if you don't have the correct version installed term recognition won't work at all.  Why would you even need to point to an older version anyway?

Regards

Paul

I don't mean to say "point to an older version" but rather point to the correct (the latest) version in situations like the case at hand. In other words, a quick way to fix something that is, no doubt, just a wrong parameter and not a systemic failure. I forgot to mention that my Termbase functionality for my current project(s) has been correctly linked to Multiterm 2017 all along, ie, adding, editing, reviewing, etc. my Termbases while translating. In other words, term recognition has been working fine all along.