Francesco Monticelli 

Try removing all of your plugins and restart Studio and try again with LC.  Don't add any plugins at all yet.  See if it works then.  

Please delete the following folders:

%APPDATA%\Trados\Trados Studio\17\Plugins

%LOCALAPPDATA%\Trados\Trados Studio\17\Plugins

c:\ProgramData\Trados\Trados Studio\17\Plugins

 Paul 

Thank you for your guidance. I have removed all plugins and deleted all the folders you listed, but unfortunately, Term Recognition still doesn't work with the Cloud Terminology provider.

I might be wrong, but considering that I am getting issues with the IATE Terminology provider as well (while my colleague who hasn't run the update doesn't), it looks like there may be an issue with the way this update connects to the network/talks to the terminology databases in the cloud?

 Paul 

Thank you for your guidance. I have removed all plugins and deleted all the folders you listed, but unfortunately, Term Recognition still doesn't work with the Cloud Terminology provider.

I might be wrong, but considering that I am getting issues with the IATE Terminology provider as well (while my colleague who hasn't run the update doesn't), it looks like there may be an issue with the way this update connects to the network/talks to the terminology databases in the cloud?

Francesco Monticelli 

Francesco Monticelli said:

I might be wrong, but considering that I am getting issues with the IATE Terminology provider as well (while my colleague who hasn't run the update doesn't), it looks like there may be an issue with the way this update connects to the network/talks to the terminology databases in the cloud?

Maybe... but given these are completely different end points it would make me suspicious of your own network connection?

I also thought that might be an issue. But I share an office with a colleague who also uses Trados Studio 2022 and connects to the same network as me. When I realized I was having issues, I told her to hold on installing the update to17.1.6.16252 for now.  She has not installed the update, and she can continue using both the IATE and the Cloud Terminology providers normally, just as I could before the update. So, I would rule out my network connection.

 Paul 

UDATE: one thing that I failed to mention: when I set up the Cloud-based terminolgy provider, I was selecting two termbases from Language Cloud: one that I created in my own account, and another one which my client shared with me from their account.

The Cloud-based terminology doesn't work if I add both termbases. If I only add one (e.g. the client's shared TB), term recognition works. Was a limit on the number of language cloud TBs set in this update?

I have finally been able to get to the bottom of this.

As of 17.1.6.16252 (apparently), the language fields must match in all the TBs you add to the Cloud Terminology provider in a project. E.g., if one termbase has en-US and it-IT, then all termbases you select in the Cloud Terminology Provider settings must have en-US and it-IT, otherwise (if. e.g. one has en-US and it-IT, and another has en-US and IT -which was my case) term recognition will stop working altogether.