Hello David Baour ,

Are you receiving an SDL PPX package? Or individual files? 

Where are you saving the files/package to after you receive them?

The more information you can provide (and screenshots) the more this helps us determine the problem.

Hello Steven,

I got a new message right now:

At the moment, I can only translate by opening one document.

Yes.

Thank you Paul! I made exactly what you suggested and it seems to be working! Now, how can I work with the two memories that are so useful to me? Is there something wrong with them? How do I proceed to retrieve their contents? Thank you in advance.

I tried to add my principal glossary and Trados immediately crashes.

However, I could add my principal TM.

David Baour

I think it would help to understand where these resources are stored.  Do you keep them on a separate drive, or in something like OneDrive or DropBox for example.  Or are they all stored on your local machine without any interference from outside influences at all?

They are all stored on my D: hard drive, my computer having 2 hard disks (C: and D:).

David Baour

Perhaps worth testing with something that is regularly causing the crash, like your termbase for example.  Put a copy on your C drive and test again using the resource in this location.  See if it's any better.

Thank you Paul, it seems to be working now! Do you know why this happened suddenly? And should I store all my my memories and termbases on the C drive?

What surprises me is that I've been working for many years backing up all my professional folders on this D drive and it has never been a problem until now.

David Baour

To be honest I have just been narrowing down the likely source of the problems based on the information you have been providing.  Studio is recommended for installation on the C: drive and to access the data on the same drive.  This is not to say we don't support other configurations but these seem likely places to start to look when a problem occurs.

Some of the message you reported above could relate to a dodgy partition (drive condition can change over time) so it might be worth backing up all your data and running a disk repair, then copy it back.  But I'm really no expert on this so it could be worth getting some advice and help to make sure your drives are all in good condition.

David Baour

To be honest I have just been narrowing down the likely source of the problems based on the information you have been providing.  Studio is recommended for installation on the C: drive and to access the data on the same drive.  This is not to say we don't support other configurations but these seem likely places to start to look when a problem occurs.

Some of the message you reported above could relate to a dodgy partition (drive condition can change over time) so it might be worth backing up all your data and running a disk repair, then copy it back.  But I'm really no expert on this so it could be worth getting some advice and help to make sure your drives are all in good condition.

Thank you, Paul, for your detailed response which caught my full attention. The reason why I initially opted to save my translation files on the D (mechanical) disk is that it has much more space than my C (SSD) disk. I will therefore at least transfer the memories as well as the terminology bases to disk C. Thank you for your valuable support.

My modest experience: since an OS reinstallation is usually devastating for the C: drive (luckily now it is rather uncommon), for years I have been storing all my TMs and all my TBs on my D/ drive and it seems that no problem ever derived from this policy.

Thank you Gérard for your answer. I finally left the problematic glossary on my hard drive D and contained myself to copy it somewhere else and to my surprise, things went back to normal. So I haven't started anything new for the moment.