Hi! Such a message started appearing during translation a couple of days ago. When it emerges, my work stops - no changes can be made. Thanks goodness I still have 2011 version where I can continue my work. Surprisingly, when I reopen my project in 2017 it becomes translatable again; however, sooner or later the error reappears again and again. Any suggestions? TIA
It's happened earlier than expected! :)
Hi Dimitriy,
I forgot to mention that it appears the error is also triggered by autosuggest.
I think a certain term in the project with the error is causing the problem.
My guess is it runs fine with others file and projects because those projects do not have that same term in them.
Basically, when the error happens, I would look up the terms in that segment in the main TB. Try to see if any of the entries look strange in the TB.
Hi Jesse,
I have the same "An item with the same key has already been added" error in Studio 2017 (14.0.5889.5) as Dmitriy.
It seems indeed triggered by AutoSuggest (AS) and linked to the MultiTerm termbase (TB).
I managed to identify a term in the segment that causes the error that:
1. also causes the error message above in MutiTerm 2017 (14.0.2184.3, MT) when I search for it using the search field;
2. is not displayed in MT’s main entry pane when I click on it in the search result list pane;
3. causes display problems in the search result list pane and the error message above when I delete it using the contextual menu (see screenshot below, top left corner).
I also noticed that MT does not really delete the entry from the termbase. It is stil in there. Repeating the actions above on the item causes the same problems. I cannot delete the entry.
Incidentally, I remember having added a synonym to this MT entry yesterday.
So I think this problem is due to MT corrupting the entry or an index.
Reorganizing the TB does not solve the problem.
This is definitely an issue for the SDL devs.
I hope they will come up with a solution soon.
Hello Jesse,
here are images from Multiterm and Studio. I tried to add a xml file, but the editor didn´t accept it.
Best regards,
Stefan
Hi all,
I'm having the same issue but I'm not using a TermBase in the project at all and the issue happens when I try to create a legacy TTX in Studio 2017 and 2014.
Any ideas, please?
Thanks,
Hi Jesse, I have the same problem, but no termbase associated with the project
Hi Jesse, I have the same problem, but no termbase associated with the project
Translate
