"Probability score": 0.9

"Question improvement suggestion": The question is well-structured and includes the error message, steps already taken to resolve the issue, and the software version. However, it would be helpful to know if there were any recent changes to the system or software, and the operating system and its version.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Tina,

It seems like you're experiencing an issue with opening sdl.ppx files in Trados Studio 2022. You've already tried updating to the latest version and reinstalling the software, which are great first steps.

Based on the error message you're receiving, it appears that there might be an issue with the package extraction process. Here's a workaround that might help:

Step 1: Rename the *.sdlppx package to *.zip and extract it to a folder with the same name.

Step 2: Navigate inside the folder. You should see a subfolder at the same level as the source and target language folder. This folder should have the same name as the package.

Step 3: Open this subfolder. Inside, you should find the actual project file with the extension *.proj.

Step 4: Copy this file and navigate a folder up, to the same level where the source and target language folders are, and paste the project file there.

Step 5: Delete the subfolder you opened in Step 3.

Step 6: Select the source and target language folder and the project file and zip them all.

Step 7: Once the ZIP file is created, rename it by changing its file extension to *.sdlppx. You have now created a new package.

Step 8: Try opening this new package in Trados Studio 2022.

Please note that this is a workaround and not a permanent solution. If the problem persists, it might be a good idea to check for updates within the application or visit the RWS AppStore for potential solutions.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

This has not worked out. If I rename the *.sdlppx package to *.zip, it won't extract anywhere since it says that the file is damaged.

 Tina Weinreben 

Tina Weinreben said:

Sorry, still no success. Kindly asking for non-AI help. Thank you.

Why not?  Did your client send you the package again?  Have they checked at their end that they are not sending you a file that is already corrupted?

The client has assigned the same package to another translator, who had no problems working on it. That's why I guess the package is ok. The problem occurs when I try to rename the package as .zip. Infact, before renaming it as zip, a warning appears, which says that changing the extension of the file might damage it. After having it renamed, it won't extract, because, just as announced by the warning, the file has been damage during the renaming process.

Tina Weinreben 

Tina Weinreben said:

a warning appears, which says that changing the extension of the file might damage it

No probleme. This is the usual warning message when renaming file extensions:

If the file has an extension docx because it’s a Word document, for example, and you rename it as xlsx, then Excel won’t be able to handle the renamed file. That’s the warning.

Tina Weinreben said:

just as announced by the warning, the file has been damage during the renaming process.

As mentioned above, the file was not damaged just because it was renamed.

In the past I’ve had issues with long file names. If you can move the ZIP to another folder with a shorter path, then you can try to extract or even view the content of the zip file in Windows Explorer.

Thanks for sharing. I have moved the zip to another folder with a shorter path.
However it does not work anyway. Since other translators are able to work with the same package, I don't think the package has been corrupted in the first place. Any other ideas on how to solve this issue?

Tina Weinreben 

Tina Weinreben said:

I have moved the zip to another folder with a shorter path.
However it does not work anyway.

How shorter?

Also, what did you do? You can try to unzip it or view the content of the ZIP in Windows Explorer. Which one didn’t work? Could you please try the other way as well?

Tina Weinreben said:

Since other translators are able to work with the same package, I don't think the package has been corrupted in the first place.

The file could have been corrupted when sent by email or on your end.

Thanks.
Let me explain step by step what I did and what happens when I try to follow the AI-instructions above.

Step 1: Rename the *.sdlppx package to *.zip and extract it to a folder with the same name. - This works, however during extraction the following error appears:

Step 2: Navigate inside the folder. You should see a subfolder at the same level as the source and target language folder. This folder should have the same name as the package. - No folder appears, but I can see the proj-file mentioned in Step 3.

Step 3: Open this subfolder. Inside, you should find the actual project file with the extension *.proj. - As mentioned there is no folder, but OK, I can see the proj-file .

Step 4: Copy this file and navigate a folder up, to the same level where the source and target language folders are, and paste the project file there. - Since there is no folder, the proj. file is already at the same level as the source and target language folders.They are already in the same place.

Step 5: Delete the subfolder you opened in Step 3. No subfolder, so I proceed immediately to Step 6.

Step 6: Select the source and target language folder and the project file and zip them all. Ok, done.

Step 7: Once the ZIP file is created, rename it by changing its file extension to *.sdlppx. You have now created a new package. Ok, done.

Step 8: Try opening this new package in Trados Studio 2022. When I try to open the new package, the following error appears:

Tina Weinreben 

ok - let's wind back a bit.

1. Please save the sdlppx file you received onto a location that is not on your OneDrive path.  The current one is:
   
   Test opening the package from the new location (that DOES NOT HAVE OneDrive in the path)
2. If that still fails please confirm that the size of the sdlppx you have is exactly the same as the one your client has.  That will help assure us that you have successfully downloaded the same file.  Although now I see the OneDrive path I am thinking that this part of the error "Unable to read beyond the end of the stream." is because your sdlppx file is cloud only and so Trados fails to open it because it has to download it from the cloud every time you open it and it fails because it's still downloading.

I'm leaning towards a OneDrive problem, but let us know what the result is of your testing.

Thanks Paul.

1. has not worked out.

However, I have downloaded the files today again and have noticed that the file size from today's download is different from the size of yesterday's file, although the client has confirmed that he has not made any changes to the upload (it was a WeTransfer).

Also, I have checked the file sizes with the client and the original file the client has, is almost twice as big as the file I have downloaded. So, not only is my file smaller than the client's one, also is the file size from today's download different from yesterday's download...

Tina Weinreben 

So from your answers it looks as though you are finding the root of the problem.  It seems you are not able to download the full package without it being curtailed in some way and this means Trados Studio cannot read it.

Given this is a persistent problem perhaps you should review your security software?  That might be the cause of your woes.  Try turning it all off while you download the file and see if it makes a difference?  Or, if you have access to another computer try downloading the file there and manually transfer it over to your working machine?

Thanks, Paul, for your help. I have downloaded both files again today without security software and it has worked out for one file, which I am now able to open and work on  in Studio. The other still has the same error, and tonight I will try to download it from another computer and see if that works. Again thanks for your help.

Thanks, Paul, for your help. I have downloaded both files again today without security software and it has worked out for one file, which I am now able to open and work on  in Studio. The other still has the same error, and tonight I will try to download it from another computer and see if that works. Again thanks for your help.