Hello Hendrik Bahre ,

After updating MultiTerm (Latest stand-15.0.6.56482) have you also updated Studio 2019? (Latest stand-15.2.6.283).

Both Studio and MultiTerm, do need to be on the latest stand. (this alone resolves many issues).

If everything is up to date, It might be helpful to know where the Termbase is stored- Locally or via a remote (FTP) server?

A similar case I have seen was due to the TB being stored on an FTP server.

The resolution (not sure if this applies in your case) here was to use network sharing and not an FTP server.

Hello Hendrik Bahre ,

After updating MultiTerm (Latest stand-15.0.6.56482) have you also updated Studio 2019? (Latest stand-15.2.6.283).

Both Studio and MultiTerm, do need to be on the latest stand. (this alone resolves many issues).

If everything is up to date, It might be helpful to know where the Termbase is stored- Locally or via a remote (FTP) server?

A similar case I have seen was due to the TB being stored on an FTP server.

The resolution (not sure if this applies in your case) here was to use network sharing and not an FTP server.

Thank you very much for your quick response!

SDL Trados is indeed also updated to the latest version (SDL Trados Studio 2019 SR2 - 15.2.6.2831). The termbases are indeed not locally stored by on a network server. However not over FTP, but a "regular" network drive (which should be SMB protocoll I guess?). Maybe it's an issue with SMB v1/2/3?

Hello Hendrik Bahre 

As the similarities in the two cases are so similar, I suspect that the problem indeed lies with the server protocols.

Might be worth asking your IT department to have a look at the configuration.

Perhaps you have the option of downloading the Termbase to your local machine (or if not create your own local termbase) to check there are no issues and to confirm its a remote connection issue.