SQLite error

Hello,


I work in a company that has an in-house translation department. All our translation files are on a common server and this was working just fine until yesterday. All our translation memories are on a common server and since yesterday, we are able to access the TM intermittently for a few minutes at a time. At other times, we have an error  message stating "SQLite error - cannot roll back. no transaction active". When this happens, the TM is inaccessible and sometimes there's a file named "journal" which appears in our TM folder. When deleted, the TM starts working again, but the file inevitable reappears and we no longer have access to the TM.


I'm not sure if this is a problem with our server or the TM. Has anyone else faced this particular situation? What can be done to correct this?

Thank you! :)

Parents
  • Hi Swathi - it would be great to have some more information about this. Can you tell us:
    * what version of Trados Studio you're using, including if/when you installed upgrades
    * how many users (roughly) will be accessing these TMs at the same time
    * does the journal file disappear if everyone exits Trados Studio
    * can you reproduce it easily with (say) two users, if you start with no problem accessing TMs, then get user A to do something and user B to do something, so as to hit the problem

    Kevin

  • Hi Kevin,
    Thanks for your questions. You'll find my answers below:
    1. We're using SDL Trados 2015 currenty. We haven't updated for a while now, so I don't think that's what is causing it.
    2. Usually we're a maximum of three users who access a particular TM at the same time. We also have, for example, a single German translator who accesses her own exclusive TM. She is facing the same problem as well.
    3. The "journal" file is sometimes deleted by one of us and sometimes disappears on it own.
    4. This morning, for example, when I opened Trados the TM wasn't working. Then, I opened the Project parameters I got an error message reading "the TM could not be opened and was deactivated". Following this, I added the TM once again and it worked for exactly one segment, before switching back to the error messaging saying "SQLite error - cannot rollback - no transaction is active".

    Hope this helps ...
  • Hi Swathi - ok, in that case, it does sound more like a problem with what's happening on that shared network drive. The 'journal' file is created by SQLite when changes are made to a TM that fall within the scope of a transaction. That's generally a pretty brief operation, after which the journal file gets deleted. I'm wondering whether there is something going on with that network drive that is stopping SQLite from being able to delete the journal file. For instance, could there be some backup software monitoring it and attempting to back up files? This could cause the journal file to be locked. If the network share is part of a folder structure within (say) a OneDrive folder on the server, for example, that could well cause problems. Similar issues *might* arise if the shared folder is subject to some other kind of real-time special processing, such as virus scanning, compression or encryption. Does anything like that sound possible?

    Kevin
  • Hi Kevin,
    You were right! This was a problem with our shared network drive. We don't use OneDrive for Trados as this has proven really problematic in the past. But it was problem with our network. Thanks for the quick responses and your help.
    Cheers!
Reply Children