Hello Edward Bradburn ,

Its always a good idea to post the actual versions of Studio/Multiterm so we can check everything is indeed up to date (support would do the same if we need to log a ticket).

If both Studio and Multiterm aren't both on the latest stand , this is known to cayuse issues.

Have you removed the Termbase from the project in Studio before reorganizing?

Where is the TB saved? Local or in the cloud?

Hi Steven,

Thanks for replying. Here is all the info you requested:

• Studio: TradosStudio2021SR1_16.1.8.4404.exe
• MultiTerm: SDLMultiTermDesktop2021SR1_16.1.1.541.exe
• Termbase is not removed from project in Studio, I had no idea this is even required? Studio was not running. Does the termbank have to be removed as well? This is an agency package, I'd really rather not go around changing their settings if I don't have to.
• TB is local, came with the agency package

I have tried a few more times and now it reorganises without crashing although I then get occasional object reference errors when using the TB in Studio.

Hope this can help to pinpoint the issue, but term recognition itself remains a huge problem in Trados, it is simply not stable for many users, including myself.

Thx,

Ed

Hi Steven,

Thanks for replying. Here is all the info you requested:

• Studio: TradosStudio2021SR1_16.1.8.4404.exe
• MultiTerm: SDLMultiTermDesktop2021SR1_16.1.1.541.exe
• Termbase is not removed from project in Studio, I had no idea this is even required? Studio was not running. Does the termbank have to be removed as well? This is an agency package, I'd really rather not go around changing their settings if I don't have to.
• TB is local, came with the agency package

I have tried a few more times and now it reorganises without crashing although I then get occasional object reference errors when using the TB in Studio.

Hope this can help to pinpoint the issue, but term recognition itself remains a huge problem in Trados, it is simply not stable for many users, including myself.

Thx,

Ed

What might help is to do a complete export of the termbase, create a new termbase (based on the old - same settings, etc. - easy-peasy during the creation process) and import the exported XML file. This helps me sometimes in similar situations. Plus a reorganization takes place automatically IIRC ;-)

Thanks Michael, I'll certainly try this in the future.

Hi Edward Bradburn,

I was going to suggest the same as Michael Schroeder :-).

Don't worry about the settings of your package, the return package that you send back in the end only contains the translated bilingual sdlxliff files and neither TMs nor termbases.

With nearly every package we get, we change the settings by adding our own TM and termbase (and update these only). The client won't notice that.

Best

Annette (from Manfred's account)

Hi Annette,

That's also good to know, although in this particular case - somewhat unusual - I am actually directly modifying the customer's termbase.

As you say, usually I'd set up my own termbase and/or TM to make sure I know what's from me and what isn't.

Thanks again for your help!

Ed