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.

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

Thank you for your help. 

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.