Hi Carla Lopes 

Did you repair the TM with the help of the app? https://appstore.rws.com/Plugin/41

Kind regards,

Yes, I've tried these options suggested by the IA:

**Step 1:** **Check for Corruption**  

- Open the affected TMs in the Translation Memory Management view of Trados Studio to see if they are indeed corrupted.  

**Step 2:** **Repair the TM**  

- If the TMs are corrupted, try using the SDL TM Repair tool. You can download it from the RWS AppStore. After installation, it will appear under the Add-Ins ribbon as "TM Repair."  

**Step 3:** **Rename the Repository File**  

- Close Trados Studio.  

- Navigate to the following location on your computer:  

 `C:\Users\[Your User Name]\App Data\Local\Trados\Trados Studio\Studio17`  

- Find the file named `Translation Memory Repository.xml` and rename it to `Translation Memory Repository_old.xml`.  

- Restart Trados Studio and check if the issue persists.  

Nothing worked...

Thank you.

Carla Lopes 

It's suspicious that all your TMs stopped working.  I note they are your D drive.  Can you try copying one or two to your C drive, not on a OneDrive path, and see if they work from there?  The message might be a red herring.

Hello, Paul.

Thank you very much! It worked! 

Also, I noticed that were created strange files ".sdltm-journal" when the TMs stopped working. Maybe if I delete them the TMs open again?

I've tried erasing the ".sdltm-journal" files and the TMs got back to life!

Thank you for your help. 

Carla Lopes 

Excellent... thanks for updating us.  The .sdltm-journal file temporarily holds the original state of the database during a transaction.  If the write completes successfully, it’s deleted.  If the process crashes or is interrupted, it remains.  This could happen for various reasons:

• Trados Studio crashes or is forcibly closed
• There is an unexpected power loss or system shutdown
• The disk becomes full or read-only during a write operation
• Antivirus or backup software locks the file
• A third-party process (like a script or SQLite browser) is interacting with the TM

External drives (your D drive perhaps, or OneDrive, Dropbox etc.) can easily lead to .sdltm-journal files being left behind if the connection is unstable or interrupted.  It’s not inherently wrong to store TMs externally, but I'd strongly recommend you don't edit them, or work with them, directly from such drives to avoid data integrity risks.  Good for backups, but not dynamically as you work.