I am facing exactly the same issue here.

Every time I open specific segments (that contains a particular term) Trados crashes. And here this also only happens with one project I work regularly.

Did you manage to find any workaround Katrien Vertommen? Any clues, Paul?

Best regards

I am working with a Studio Pkg sent by the client. I plug my own TMs and TermBases. There are 2 specific segments that, whenever I entered them (i.e., before typing or confirming them) SDL Trados Studio...bufff! Studio shuts down and crushes without further warning.

Very very annoying indeed.

After reading quite a few threads on the matter, I tried disabling the match repair options but it didn't word. 

However, removing the Multiterm termbase from the project did the trick. It is not ideal but is what I need at present to meet my deadline.

I can believe that a software that costs so many hundred euros doesn't have a better error-handling routine that prevents this crashes from occurring.

Katarína Tršová

Pease can you confirm exactly what the latest version numbers are?  I'm sure you're right... but then it won't be the first time someone said they were on the latest and they actually were not, so I'd prefer to check.

Katarína Tršová said:

IATE realtime plugin not working/working only partially

Please can you provide details of the problem here and what version you are using?  This is a tricky plugin as it's also affected by the EU and not just anything we do.  We work closely with the IATE team on this and currently it should be working faultlessly and this is the first complaint I have heard.  So I'd like to get to the bottom of this.

Trados Studio 2021 SR1 - 16.1.8.4404

SDL MultiTerm 2021 SR1 - 16.1.1.541

IATE realtime plugin not working/working only partially: It does not highlight the terms in my source segments (almost not at all). It does look up the terms in the IATE database after I select them manually in my source segment and choose Search IATE from the menu.

PS Could you do something with the TM upgrade option which was available in e.g. Studio 2017 in one step when opening the project. I usually get about 5+ TMX which I then have to convert one by one through Glossary Coverter or - worse - recreate them by creating new TMs and importing the received TMXs.

Many thanks for your efforts.

Katarína Tršová

ok - versions are good.  Ca you provide a sample termbase with this problem so I can reproduce the problem?

Katarína Tršová said:

IATE realtime plugin not working/working only partially: It does not highlight the terms in my source segments (almost not at all).

Can you provide some sample text where this happens?

Katarína Tršová said:

PS Could you do something with the TM upgrade option which was available in e.g. Studio 2017 in one step when opening the project. I usually get about 5+ TMX which I then have to convert one by one through Glossary Coverter or - worse - recreate them by creating new TMs and importing the received TMXs.

No... but you can.  The solution to this is to install the Compatibility and Migration Power Pack from the appstore:

https://appstore.sdl.com/language/app/sdl-trados-compatibility-and-migration-power-pack/1101/

It's covered in the release notes for 2021.  This feature was part of a lot of legacy code that was removed to improve the installation experience for the core product and also to allow the development team to stop having to deal with legacy code as they work on improving the product going forward.  You can also find more on this here:

https://multifarious.filkin.com/2020/08/15/some-you-win-some-you-lose/

Paul said:

No... but you can.  The solution to this is to install the Compatibility and Migration Power Pack from the appstore:

Please what version exactly should I choose when I download the app?

Paul said:

Can you provide some sample text where this happens?

"Formal conclusion is expected still this year allowing for the subsequent signature and ratification of the Protocol. The Commission will work with the European Parliament and the Council to enable Member States to sign and ratify the Protocol as soon as possible....Integrating Artificial Intelligence (AI), Big Data and High Performance Computing (HPC) into security policy without weakening the effective protection of fundamental rights is essential to increase safety and security....Artificial Intelligence can offer tools to support law enforcement authorities in their fight against crime and terrorism, keeping pace with the fast developing technologies used by criminals and their cross-border activities"

Edit: It does highlight some of the terms here and there (BTW I did not check any fields so it should serach the entire IATE database

Katarína Tršová

Katarína Tršová said:

Please what version exactly should I choose when I download the app?

Well... you told me what version of Trados Studio you have so I would say this one:

Why is this confusing?  Just want to make sure we haven't missed something obvious here.  If you use the integrated appstore you'll get the right one automatically seeing as you have the latest version of Trados Studio installed.

Katarína Tršová said:

BTW I did not check any fields so it should serach the entire IATE database

This may not be not possible to get all the same results as we do have some restrictions imposed by the IATE API.  However, please make sure you read the wiki here which may help with your settings:

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3390/iate-real-time-terminology

The load placed on the IATE servers when translators use this app is potentially huge because we are not just looking up the odd word or sentence here and there.  We are looking up every word in every sentence all the time.  So we have had to agree with the IATE team on the best way to manage this so we don't bring their servers down!

I'll have a play with your text later, thank you for that.  If we think we can improve on it without causing a problem then we will.

Paul said:

Well... you told me what version of Trados Studio you have so I would say this one:

Why is this confusing?

Trados Studio 2021 SR1 - 16.1.8.4404 is the version of my Trados Studio so, yes, it was confusing to me...

Paul said:

However, please make sure you read the wiki here which may help with your settings:

https://community.sdl.com/product-groups/translationproductivity/w/customer-experience/3390/iate-real-time-terminology

I will.

Anyway, I hoped it would highlight all IATE terms which was waaay to much to expect from a plugin, it seems. Still, I definitely hope that at least the English/Slovak version yields better results. In fact, this is the reason why I bought the latest ungrade (to no avail, helas)

Thank you for you time and help!

Katarína Tršová

Katarína Tršová said:

Trados Studio 2021 SR1 - 16.1.8.4404 is the version of my Trados Studio so, yes, it was confusing to me...

ok.  So this means:

16 - is the major version (2021)
.1 - is the service release version and will change when we have new service releases (SR1)
.8 - this represents the CU number (CU8)
.4404 - this is our internal build number

So you have 2021 SR1 CU8, hence the last option as it's greater than CU7.

Katarína Tršová said:

I hoped it would highlight all IATE terms which was waaay to much to expect from a plugin, it seems

It's not too much for a plugin of course!  The problem, as I did try to explain to you, is that the use of the plugin increases the load on the IATE servers by a magnitude so large it could bring down their servers.  So it has to be deliberately restricted.  You make it sound as though the plugin is simply too trivial a tool... but the opposite is actually true.

The latest upgrade actually improved things a lot for several reasons:

====================================

Release date: 25th May 2021

Version 3.6.9.1 for Studio 2021

• Implemented a new search option (18: Light Any Word) provided with the latest release of the IATE API to optimize search procedure.
• Refactored the code base; introduced new concepts: Connection and Inventory providers
• Introduced a new Sqlite provider
• Removed the dependency on SQL Server
• Apply TermRecognitionOptions.SearchDepth value from the project settings when searching for terms against the IATE API

=====================================

Paul said:

You make it sound as though the plugin is simply too trivial a tool... but the opposite is actually true

I would never dare to do that and thank you for all your efforts.

Paul said:

whether or not we can have a copy of the offending termbase to reproduce the issue?

Yes, you can. Can I send it to you privately?

Katarína Tršová

Katarína Tršová said:

Can I send it to you privately?

Of course, you can send it to pfilkin@rws.com

Katarína Tršová

Katarína Tršová said:

Can I send it to you privately?

Of course, you can send it to pfilkin@rws.com

Katarína Tršová

Thanks for sending me the termbase.  So far I could not see any specific problems with this termbse, although I did note a couple of things you could try changing and see whether it helps as MultiTerm has been known to have problems in this area in the past:

1. remove the accented characters in the termbase file name.  So change the ý to a y for example.
2. do the same in the "friendly name" in the termbase definition.  So under Termbase Management -> Definition -> Edit and then in Step 2 of the wizard.

I can't say this will fix everything, but it's worth trying.

Also make sure that your termbase is not connected to an external drive, or in a folder where it gets synched in real-time with somewhere such as OneDrive or Dropbox.  These sort of mechanisms can cause problems because fundamentally the termbase is only a Microsoft Access database and it's not designed to cope with these sort of requirements.

If you also have a file where you can reproduce the problem of Trados hanging when working with this termbase then that would also be really useful.  If I can reproduce the problem then we can more easily identify what's causing it.

Paul said:

If you also have a file where you can reproduce the problem of Trados hanging when working with this termbase then that would also be really useful.  If I can reproduce the problem then we can more easily identify what's causing it.

I will send it to you. I would really like to know what causes the problem. Trados crashing or freezing with files has happened before but I always thought it was because of the TM (oten very large) not the TB...

Paul said:

1. remove the accented characters in the termbase file name.  So change the ý to a y for example.
2. do the same in the "friendly name" in the termbase definition.  So under Termbase Management -> Definition -> Edit and then in Step 2 of the wizard.

I can't say this will fix everything, but it's worth trying

So far so good. It might have helped: so far it has not crashed. I used a simple renaming trick in the past, without paying attention to the punctuation marks though and it helped too (for some time). Thanks.