• State Verified Answer
  • Replies 3 replies
  • Subscribers 47 subscribers
  • Views 1628 views
  • Users 0 members are here
Options
Related

Terms not recognized in Studio 2017 using Multiterm Server termbase (Groupshare 2017)

Daniel McCosh

Hi,

Term recognition has stopped working for us in Studio 2017 when working with online termbases for terms we know are in the termbase on the MT Server (Groupshare 2017 SP1). A file-based version of the same termbase works without problems (so there don't seem to be any incorrect term recognition settings in Studio or incorrect language settings. The project language is de-de, en-gb and the termbase languages are set to "German" and "English", however this was also the case for the file-based termbase which works fine in Studio]. We are seeing this issue on all server termbases. The server is connected and available. I can also search for the term in the server-based termbase and it is displayed - unfortunately the term recognition still does not deliver any results in Studio.
I've just tried reorganizing the server-based termbase from Multiterm Desktop. This has not solved the problem.
We have the latest CUs installed for both Studio and Groupshare 2017 SP1.
I'm a bit stumped with this one - does anyone have any ideas?

Regards,

Daniel
Rate translation
×
Suggest better translation
×
Parents
  • 0
    We found a problem where by if the first termbase (also server based in our case) listed in the project list didn't contain all languages being used on that project then for those missing languages the term recognition would not work even if other termbases listed at a lower priority did contain those languages. A work around was to include a termbase with all languages at the tip of the termbases list, this could be a termbase with just a single term for each language. If you have more than one termbase associated with your projects this could be worth checking.
Reply
  • 0
    We found a problem where by if the first termbase (also server based in our case) listed in the project list didn't contain all languages being used on that project then for those missing languages the term recognition would not work even if other termbases listed at a lower priority did contain those languages. A work around was to include a termbase with all languages at the tip of the termbases list, this could be a termbase with just a single term for each language. If you have more than one termbase associated with your projects this could be worth checking.
Children