Trados Business Manager
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
I have just downloaded and installed the LATEST versions of Studio and Multiterm and I'm having the following problem with Multiterm.
Whenever I'm working on a project with a term base loaded, it works fine for some time. Then, at some point, the term base disconnects from the project and its terms no longer appear in the Term panel. When I open the project settings, the error mentioned in the post title pops up (framed as a question). If I click "yes", it keeps popping up, now framed as an error. I can't do anything from then on apart from removing the term base, closing the project, reopening the project and loading again the term base. Until it all happens again at some random moment.
My software is up to date:
SDL Trados Studio 2021 SR1 - 22.214.171.12496
SDL MultiTerm 2021 SR1 - 126.96.36.1991
I also tried to uninstall, reload it and install it again.
Note that this also happens with termbases built with this very Multiterm version.Thank you for your help.
Hello Valentina Luridiana Galati ,
Were you already working on this project when you updated Studio/MultiTerm?
If you create a new project, do you still observe the same behaviour?
Where are your Termbases saved? Locally or in the cloud?
I would perhaps suggest first a Studio Repair-
You can also try SDL Freshstart
and ensure that both Studio and MultiTerm are added to your AntiVirus exceptions list.
Hi Steven,Thank you for your swift reply.
The problem described happened with three projects (which are literally the only ones run on my brand-new Trados 2021): all of them where created anew, and two of them were very small practice projects (simple doc file of less than 20 segments, termbase with 5 term pairs introduced manually into multiterm).
Everything was saved locally.
In case this is relevant, I'm running my Windows on a virtual machine on a Mac and I am under the impression (though not sure) that the problem tend to arise whenever I leave the computer idling for a long period.I will explore the possibilities you suggest and let you know what happens. Thank you for now!
Update 1: I tried Repair, but the path mentioned on the SDL page (i.e.
is not what I see on my computer (which is a straight "Uninstall"). I haven't done it as I have already tried it once, to no avail. I will try now the other suggestions and keep you updated.
Update 2: I'm not even able to download Freshstart. Whenever I try to download it, I'm urged to login; I then login into my account but, as soon as I click on the appstore, I'm logged out and the whole cycle starts again. I wondered if they were two separate account spaces (say, SDL customers vs developers), but if I try to sign up it won't let me as my email is recognized.So another cul-de-sac.
We now have exactly the same issue.
I'm running the latest versions of both Studio and Multiterm 2021 SR2. I created a termbase this morning and have now added it to a newly created Studio project. And now I keep getting that error about the termbase being created with an older version of Multiterm.
Is there a known solution for this issue by now? And please don't mention the words 'Repair' or 'Freshstart'. We've already been having issues lately with Studio crashing after app updates and I really don't feel like re-configuring Studio again...
Hello! Just curious... Is there ampersand in the path where the termbase is stored?
Apologies for the late reply.
No, no ampersand in the path. No accented characters either. Not even a space. Just a-z characters and an underscore.