Hello Claire Carrion 

My first suspicion here would be that the path (to where the project is stored) is corrupt.

Have you tried removing the project from Studio and then navigating to the project folder and clicking on the .sdlproj ?

This should then reopen the project in Studio-

Hello Steven, Thank you for your answer :) Maybe this is a stupid question, but is there not a risk of loosing what I have done before on this project if I remove it from Studio? Also, I only experience this problem with the last two sliff files that I had not opened yet before the update. Apparently, the xliff files that I have translated already (in the same folder) are completely OK. I have also noticed that the icon of the two problematic xliff files appears slightly different in the Windows viewer. I have just asked my client if they could re-send me these two xliff, hoping that just replacing them will solve the problem. I will keep you updated.

Hello Steven, Thank you for your answer :) Maybe this is a stupid question, but is there not a risk of loosing what I have done before on this project if I remove it from Studio? Also, I only experience this problem with the last two sliff files that I had not opened yet before the update. Apparently, the xliff files that I have translated already (in the same folder) are completely OK. I have also noticed that the icon of the two problematic xliff files appears slightly different in the Windows viewer. I have just asked my client if they could re-send me these two xliff, hoping that just replacing them will solve the problem. I will keep you updated.

Hello Claire Carrion ,

Removing the project from Studio, shouldn't cause any issues whatsoever.

Once Projects are complete- they should be removed from the list as good housekeeping.

Claire Carrion said:

Also, I only experience this problem with the last two sliff files that I had not opened yet before the update.

I suggest you test the files individually by setting up a single file translation.

Open the file- then close immediately (Save target As) without translating anything- If there are issues at this stage, then you can be fairly sure the file is faulty.

It would be good if you could post an image of the icons- this may tell us something.

Hello Steven, thank you for your answer

I have removed the project from Studio and then clicked on .sdlproj, but unfortunately, this did not help. I still get the same error with the two problematic files. Also, I cannot create a return package with the files that were not problematic, as I receive the following message:

I mentionned in an earlier message that the problematic files appeared differently in Windows. Now just one of them does and the icon is as follows:

It is the one with the blue double arrow. I found out that it had to do with compression, so I unchecked the compression option in the file properties, but it did not help either.

The strange thing is, I can open the two problematic files without any problem, it is just that I cannot save the modifications. 

Same thing for the non-problematic files: I can work on them and then save the changes, but it is not possible to create the return package...

All this started with I updated to the new version of Studio 2019.

I hope all this info can help

Hi Claire Carrion

Perhaps you can try this:

1. Make sure the project has been removed from Studio
2. Copy the entire project safely to a new location and delete it from the projects folder
3. Open the original project package you received so it recreates the project in Studio
4. Copy the sdlxliff files from your safely stored project into the new target language folder so they replace the ones that are in there

That should get you a new project with your updates. Now try and create your return package,

Thank you Paul,

I have tried this and it did not work in a first place... But I finally found the solution. It had nothing to do with the update or with Studio... The path was too long. The two problematic files had a very long name, and I guess that was the issue. So, I followed your advice again, but this time I put the project folder directly on the desktop. And now everything seems to work perfectly :) 

So, a big "thank you" to you, and to Steven, for the help!

It's old news, but Claire, you just saved me. I wasn't able to save either on a long, complicated project, and all I did was shorten the file name to get Trados to save it. Phew!