Trados Studio 2015 file cannot be opened anymore

I was working on a large project in Trados 2015 – the project consists of approximately 18K segments – and after a while “System out of Memory Exception” error messages started to pop up. Fortunately it did not affect the project since I was able to continue my work after restarting the computer every time the above message occurred (4 times in 2 days).
Today however, a different error message popped up when I clicked on “Save”: “An error occurred while parsing EntityName”. After that I was no more able to open my file or do any other actions with it.
The Hungarian SDL vendor suggested the following possible solutions to no avail:
kb.sdl.com/
producthelp.sdl.com/.../6574.html
I did as I was instructed but the line and position in question – which is by the way the very last position of the last line - does not contain any ampersands.
We also tried deleting settings as an alternative solution, but it did not help either.
Could you suggest any other possible solutions so that I could continue working on this file?
Thank you very much for your help.
Istvan

Parents
  • Hi and thank you for the responses.
    We have now managed to restore a slightly earliery, still uncorrupted version of the files from our backup system. Fortunatelly no work is lost, everything is either in the restored project file or the TM.
    It turned out that after the crash the project file was truncated to about a third of its original size.
    I am not sure how to carry on working with this project, as it seems that if we keep on working in the same file, the crash / truncation will just repeat itself in a few hours; I suspect it is because the file is just too large.
    Do you have any suggestions?
    Thanks,
    Istvan
  • Hi István,

    The large file would be non-performant, but should not be the cause of the crash. My guess would be that when working with such a large file many things will take longer than normal to complete and if you happen to have external software such as security applications, or disk cleaners running in the background; or maybe you have the files on a separate drive that is impacted by connectivity occasionally then the file could be impacted by one or more of these things, possibly causing it to become truncated.

    Perhaps you can check some if these things, or cut the file down into bit sized chunks for the translation and then piece it together again afterwards.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • Hi István,

    The large file would be non-performant, but should not be the cause of the crash. My guess would be that when working with such a large file many things will take longer than normal to complete and if you happen to have external software such as security applications, or disk cleaners running in the background; or maybe you have the files on a separate drive that is impacted by connectivity occasionally then the file could be impacted by one or more of these things, possibly causing it to become truncated.

    Perhaps you can check some if these things, or cut the file down into bit sized chunks for the translation and then piece it together again afterwards.

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children