Hello Gilles Snoeck ,

TM's are not designed to be shared so there are a number of things that might go wrong.

The following article will explain the limitations of doing so and also how best to do this to prevent many issues arrising.

gateway.sdl.com/.../communityknowledge

Hi Gilles Snoeck

While isn't wrong in that sharing file based TM's tend to be problematic and we advice that it should be avoided, we also understand it happens from time to time.

Perhaps you can explain more about how you share the TM's and what you do with them?
It could suggest improved ways forward for yourselves moving forward. 

But it does not change the fact you are stuck and its vital we get your TM stability back on track. 

So, do you still get the same error if you move/make a copy the TM local to your machine (example desktop)??

If yes:

I dont have a lot of history with this particular error, but I would suggest you try the following (with your colleagues help!)

1. See what you can run under Performance and Tuning as well as under Fragment Alignment.
Such as Recompute Fuzzy Index Statistics 

My reasoning for this is to ensure if there are anomalies we try address them within the TM itself.Historically for some, an export - recreate TM would be required. However all of this is on the basis someone can actually open the TM. 

2. While the error is not the same, this article has some good troubleshooting tips: Error message when opening/editing a translation memory in SDL Trados Studio - Database disk image is malformed

Let us know how you get on

Lydia

Hi Steven, hi Lydia, 

Thank you for your ansswers !!

So, it seems the problem came from the fact that my colleague uses a different version of Trados than me (Studio 2019 and i'm on 2021).

We found a solution by him saving his TM to an .xtm instead of .sdlxtm and then I used the « Upgrade TM » function to convert the .xtm back to a .sdlxtm that my version of Trados can open.

And now it works perfectly !! 

:)

– Gil