Hello Christina Mausolf ,

I believe the error

Unknown said:

he translation memory data file engine returned an error: database is locked.

Have you tried removing the TM from the project and adding it back in- or creating a new project?

Maybe try repairing the TM with the following app

https://appstore.sdl.com/language/app/sdltm-repair/298/

If this all fails, you may need to export to TMX and then reimport into a new memory.

Borrowing this old thread, as our team is experiencing the same problem with Trados Studio 2019.

I'm guessing our VPN-connection is the culprit for most of the sluggishness in Trados, but this particular problem comes up at random and both with and without the VPN-connection. It also affects several different memories, which makes me think it's not all of them being corrupted.

It does not occur all the time, and when it does, we can still continue working, albeit with a slow and freeze-prone Trados.

Is there any other possible explanation to this, or, if it is indeed a matter of several corrupted TMs, what could be the cause of this?

Thanks.

Hello Henrik Andersson

You mentioned-

Henrik Andersson said:

but this particular problem comes up at random and both with and without the VPN-connection.

-where are the TM's stored? presumably on a remote server?

If you are accessing the TM's remotely, there are a few things I would try first-

1. Ensure both Studio and MultiTerm are whitelisted in your AntiVirus software.
2. Repair the TM (using the app as suggested above)
3. Export the TM to TMX and reimport into a new TM
4. If you are using multiple TM's- create a test project and use just one TM at a time to see if you can narrow the issue down to the TM that might be causing the issue.

Also if you are able to, maybe download the TM locally and see if the problem still occurs.

Please let us know if this helps-

Hello Henrik Andersson

You mentioned-

Henrik Andersson said:

but this particular problem comes up at random and both with and without the VPN-connection.

-where are the TM's stored? presumably on a remote server?

If you are accessing the TM's remotely, there are a few things I would try first-

1. Ensure both Studio and MultiTerm are whitelisted in your AntiVirus software.
2. Repair the TM (using the app as suggested above)
3. Export the TM to TMX and reimport into a new TM
4. If you are using multiple TM's- create a test project and use just one TM at a time to see if you can narrow the issue down to the TM that might be causing the issue.

Also if you are able to, maybe download the TM locally and see if the problem still occurs.

Please let us know if this helps-