Hello Alexandra Blatz ,

I don't think the issue lies with the Studio/MultiTerm upgrade as otherwise we would be seeing many more cases.

Please first check your project package/settings and ensure that the TB is actually included.

Next check the server settings and ensure this is up to date  and that you have the correct permissions (you should possibly speak with your client regarding this).

Hello,

Thank you for your prompt reply, Steven. Well, I assume that the server settings are still up to date, as otherwise the TM connection would also fail, wouldn't it? So I can work with the client server-based TMs in Studio 2019 SR2, but no longer with their termbases since I started with 2019 SR2 last Wednesday. This concerns different PMs with different projects - always the same - TMs yes, termbase with term recognition: no. The termbase project settings now always look as follows:

In front there is the termbase name, followed by "(default)".

Thanks in advance and regards, Alexandra

PS: I've read in the meantime that there seem to be various issues with SR2 and that it is recommended to wait with the installation. Unfortunately, I've installed it now, and this issue is quite annoying. I really hope it can be fixed.

Hi Steven, hi Angelo,

Sorry I have not yet contacted the support team, but will do so asap. I'll let you know of the outcome.

Best, Alexandra

...perhaps we will know more within next 2 days.

Opened a support ticket.

Your request has been submitted.

We normally respond to requests within 2 working days using the email address / phone number supplied. However, if you require a license reset we will endeavor to respond within 1 working day.

P.S.: Repair Installation no success.

Hi Steven and Alexandra,

Something strange happened to me yesterday. I could add a new term, but when I wanted to add another one I got the error message again.

Multiterm is up to date, repaired, etc.

I will install the new beta today (Multiterm AND New Studio), let see what happens, I will keep you posted.

Regards,

Angelo

Hi and Alexandra Blatz,

I just tried with the beta CU5 of Multiterm and the problem is still there.

Regards,

Angelo

Hello Angelo Caltagirone Alexandra Blatz ,

Thanks for the update.

The support ticket is in the queue and will be looked at asap.

Once I have some news/updates I will get back you.

Hello @Alexandra Blatz Angelo Caltagirone

The issue you are encountering is caused by trying to connect to a Server termbase located on a GroupShare 2014 server. 

Please follow the steps from this article https://gateway.sdl.com/apex/communityknowledge?articleName=000011467 

Kind regards, 

Iulia

Hi Iulia Dinca,

sorry, but I have GroupSahre 2017 SR1, the last CU installed, so it cannot be Groupshare 2014.

Kind regards,

Angelo

Hello Angelo, 

I wanted to reply only to Alexandra's question. That solution was tested for the situation that she is encountering. 

Can you please backup your Config file, check the solution and let me know if it helps?

Thank you, 

Iulia

Hello everybody,

I am fine now. Thank you,

Alexandra

I just wanted to report that with the new CU5 beta 1 and the new Multiterm CU5 Beta the problem is gone, I can add and edit a record in the Multiterm TB within Studio without errors.

I just wanted to report that with the new CU5 beta 1 and the new Multiterm CU5 Beta the problem is gone, I can add and edit a record in the Multiterm TB within Studio without errors.