"attempt to write a readonly database"

Question

I began having in-app errors with my two main databases (read and update). 
 I ran the SDLTM app, which failed to repair them. 
 I exported them and imported them back to 2 new TMs. 
 They seemed to work fine, however file preparation time became very, very long. 
 I assumed that the reason for that was that the two new TMs were read from my Studio 2022 translation memories folder whereas my other, older, TMs (read only) were being read from my Studio 2019 translation memories folder. 
 So, I copied all my read only files from the 2019 folder to the 2022 folder, in the hope that the process would become faster. 
 However, not only it did not become faster, I am now getting a bizarre 'read-only' error message when preparing a new project concerning the two NEW translation memories which I recently prepared and were workng just fine. 
 I am not sharing my TMS with anyone, and I disabled Google Drive backup, being aware of the issue with that. 
 I am using the latest version of Studio 2022 
 
 How and why that type of write violation occur with a brand new TM? How do I repair this ?

Lydia Simplicio · Answer

Hi Shmuel Pfeifel Very odd error and while I did find some articles - non seemed to match your exact use case. So my thoughts are: 
 
 You were able to export the TM data into new TM's 
 You then recreated TM''s in a 2019 location but then moved them into something more local for 2022 (not that it is often needed as users save TM's all over the place) 
 However you found they responded quicker, which is interesting as I am now wondering if some PC security scan is being overly sensitive 
 Now you can do much at all with your TM's. 
 Can someone else see if they can work with your TM's to identify/verify if its a local issue or TM specific? 
 What if you put the TM's to your Desktop - just to help troubleshoot potential windows location related influences 
 
 So what I suggest is: 
 
 Disable the User Account Control (if not already disabled) 
 Check and add an exception for the products' relevant folders and file types to your AntiVirus - given you are now reliant on 2022 See KB for instructions 
 With the report you managed to do between your original and new TM's - create new TM's in your preferred location - 2022 
 
 If you feel your TM is corrupt and SDLTM has't helped then you could try use TM Fusion for Trados, to see what is salvageable/corrupt and to try fix it yourself. But please always back your data - even if you think its corrupt regardless! 
 I hope this helps a bit - such a worry when our TM's are not behaving. Please update so we know how you get on Lyds

Trados Studio > 1. Trados Studio

"attempt to write a readonly database"