Sarah Bichot

I had a chat with support this evening and they suggested you may have a corrupted memory that you're trying to add in Studio or perhaps it's linked in a template.

So please also try to reset the TranslationMemoryRepository.xml from

C:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\15.0.0.0

Lastly, you should try and open the TM’s you use normally in Studio.  The one which is corrupted should throw the error message.

Hi Paul,

Thanks for  looking into my problem. I tried resetting/renaming the App Data\Roaming 15.0.0.0. folder by adding _old.

I could then restart Studio, and open a project, but as soon as I started to do something I got an error message of "cannot open translation memory view" and Studio crashed again.

Then I did the same reset/rename of the App Data\Local 15.0.0. folder and again while I could restart Studio once, and also managed to upgrade the TM that had an upgrade notification, after that one action Studio crashed again.

So I'm back to square one, with the "file is not a database" message when I try to open Studio 2019.

Another problem I noticed last week was that Studio seemed to have generated TMs with the same name as the TMs I had but with [conflit] in brackets after the name. I did a tmx export of these TMs and then reimported the tmx file back into the original TM. Perhaps I shouldn't have done, and this is what has corrupted the TM?

Should I dry to uninstall and download and install a new version of Studio?

Thanks in advance for your help - and happy Easter weekend wherever you are - especially if you are working under lockdown.

Sarah

Hi Paul,

Thanks for  looking into my problem. I tried resetting/renaming the App Data\Roaming 15.0.0.0. folder by adding _old.

I could then restart Studio, and open a project, but as soon as I started to do something I got an error message of "cannot open translation memory view" and Studio crashed again.

Then I did the same reset/rename of the App Data\Local 15.0.0. folder and again while I could restart Studio once, and also managed to upgrade the TM that had an upgrade notification, after that one action Studio crashed again.

So I'm back to square one, with the "file is not a database" message when I try to open Studio 2019.

Another problem I noticed last week was that Studio seemed to have generated TMs with the same name as the TMs I had but with [conflit] in brackets after the name. I did a tmx export of these TMs and then reimported the tmx file back into the original TM. Perhaps I shouldn't have done, and this is what has corrupted the TM?

Should I dry to uninstall and download and install a new version of Studio?

Thanks in advance for your help - and happy Easter weekend wherever you are - especially if you are working under lockdown.

Sarah

Sarah Bichot

Did you also try this?

Paul Filkin said:

So please also try to reset the TranslationMemoryRepository.xml from

C:\Users\[USERNAME]\AppData\Local\SDL\SDL Trados Studio\15.0.0.0

Lastly, you should try and open the TM’s you use normally in Studio.  The one which is corrupted should throw the error message.

Yes, as outlined in my previous reply.

Sarah Bichot

In this case I suggest you log a case.  This can be achieved really quickly using this link:

gateway.sdl.com/liveagentlicensing

You have two options:

1. Submit a case using a webform
2. Use live chat to get a licence reset

You want to use the first option and make sure that you refer to this thread so the teams can see what you have tried already.

Thanks, I've done that.