Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
I have been working on a term base in Multiterm for the past months without any problem (other than working slightly slower when connected to VPN). However, a while ago I received the error message below when adding a new entry:
[One or more errors occurred]
This has become a recurring incident, as whenever I try to add a new entry I get the same message from the software and the updates are not saved correctly. I have installed the latest updates of Multiterm and the problem persists. Also, I have tried to get in touch with general IT, who suggested raising this issue here. Any advice/help? Thanks in advance!
Lucía Diaz Vilariño
Can you tell us where this termbase is stored? You mention VPN so is this a GroupShare server termbase, or a Language Cloud termbase, or a local termbase shared across a network?
Hi Paul. The termbase is stored directly in the driver (CSS Madrid DLS)
What happens if you put this on your local machine? MultiTerm is not supported at all for working with external drives in this way. People do it, but it's not reliable.
Well, it could work when working locally, but we are several people on the team working on this, so we need it on the external drive so as to be in sync. My colleagues don't have the problem I mention above, so I am guessing it has to be something to do with my computer, as Multiterm stopped working propberly out of the blue...
Lucía Diaz Vilariño said:Well, it could work when working locally, but we are several people on the team working on this, so we need it on the external drive so as to be in sync.
Really, not supported at all. GroupShare or Language Cloud would be the way to go if you need to share reliably.
I have tried to make a local copy of the glossary's folder and work on it locally, but the problem persists (same error message pops up). So I am guessing the problem is not where the glossary is stored but rather a problem with the software installed in my computer?
Hi again, I have uninstalled and reinstalled both versions (2017 and 2019) of Multiterm and tried to make a local copy, but I still get the same error message "one or more errors ocurred". Any ideas about why this keeps happening?
Can you confirm you have these versions installed (Studio and MultiTerm if you use both products):
SDL Trados Studio 2017 SR1 - 14.1.10018.54792SDL MultiTerm 2017 SR1 - 220.127.116.11461
SDL Trados Studio 2019 SR2 - 18.104.22.16849SDL MultiTerm 2019 - 22.214.171.124482
At first glance I notice in this entry a couple of odd facts. "PROTOCOL NUMBER" as the name of a language? So if you click on "Add Term" do you add a term to a language called "PROTOCOL NUMBER"? In addition, you have the "Entry Id" field empty, which is even more perplexing. An "Entry Id" comes into existence when you add the first term in whatever language your termbase includes. According to this snapshot. you have a term already, which is "test". Why is it not showing any "Entry Id" then? That cannot be possible. At least not to me and to what I know about the structure and functioning of a MultiTerm termbase. If you wish, I can take a look at your termbase.
Hello, apologies for the late reply. I have checked and I have installed those versions of Multiterm, I dont normally use Trados.
Hello. That is indeed how we have set it up from the beginning, as we need the protocol number as an extra "language",let's say, so we have the protocol number as a fixed entry (as the "source" language) and then the translations that we have available for that protocol number.
Regarding the entry ID, I understand your point and I see why that can be an issue on the correct functioning of Multiterm. I cannot say why it was not properly shown on my first message on this thread; however, the same error message pops up anyway when the Entry ID is correctly added, as the picture below shows:
I would actually be really grateful if you could take a look at this termbase and see what could be failing. My team members have not experienced this so far (although they don't usually work with this termbase). I will be OOO for the next couple of weeks, but let me get back to you after that and check. Would this be ok?
In my opinion, you are using MultiTerm is a manner counter not only to the very nature of how MultiTerm works but also counter to the structure of a termbase. Sort of your are trying to insert a round peg into a square hole. With that strange, to say the least, setting I'm not sure if I would be able to help you.
Lucía Diaz Vilariño said: Entry ID is correctly added
Every Entry ID is handled automatically by the system. The user does not have to deal with them and/or worry about them.
Lucía Diaz Vilariño said: I have uninstalled and reinstalled both versions (2017 and 2019) of Multiterm
You need not reinstall MultiTerm (or any Windows program, for that matter) to fix a faulty file.
Ozzie O said:At first glance I notice in this entry a couple of odd facts. "PROTOCOL NUMBER" as the name of a language?
Thanks Ozzie O I didn't even notice that. Indeed a very odd way to work.