Unable to open project package downloaded from a FTP Studio 2019

Question

I am unable to open a package a client has sent me via FTP. After unzipping the package, I first receive this message: 
 
 I am still able to continue but then receive another message and the package won't open: 
 
 The client has resent the package, I have renamed packages and renamed folders but to no avail. She has sent the package to translators of other languages without any problems. Any suggestions?

Ian Keith Jones Williams · Accepted Answer

I have managed to reinstall Studio 2019 a third time and now it Works. Thanks for your help everyone.

Paul Filkin · Answer

Ian Keith Jones Williams 
 There is a known issue with packages where the filenames contain umlauts and it should be resolvable by using Studio 2019 SR1 CU3 throughout the supply chain. Alternatively if you recreate the package without using umlauts in the names then it should also be fine. 
 You could also unzip the package and use the content manually? 
 SDL updated a third party library used for decompressing packages and this provides better support for umlauts in file names. However that improvement causes problems when using older versions of SDL Trados Studio.

Oana Nagy · Answer

Hello Ian Keith Jones Williams , 
 It appears from your screen shot that the actual path (appdata/temp) is a little suspect and i suspect the unzipping of the file is not working properly. 
 Could you let me know the exact extension type of the package please- for example .zip or .sdlppx and also provide a screen shot of what you see in the downloads folder- eg

Paul Filkin · Answer

Evzen Polenka 
 Well, we don't update components in the technology to force users to upgrade. That's silly. 
 The problem has arisen because we updated many of the compnents in CU3 that were well overdue and needed to be using the latest libraries to ensure we can support our customers efficiently. So yesterday we also updated 2017 to SR1 CU16 and this also updated the components there. So this means that all supported versions of Studio are compatible. 
 But to come back to your comment, you well know that software is end of lifed and we can't keep providing cumulative updates to old versions so they remain supported. So instead we ensure the current supported versions are fine and this is 2017 and 2019. So if users are on older versions than that and come across this problem then yes, they should upgrade. But this isn't because we're forcing it in the way you are suggesting. If they want to continue working with versions that are no longer supported then the workarounds will need to become part of their process.

Paul Filkin · Answer

Evzen Polenka said: Just wanted to publicly remind that updating a software may be pretty complicated thing... and that not everybody is a freelance translator with a single notebook, who can (and does) install anything anytime. 
 I absolutley agree with you here Evzen. My own background prior to SDL was Enterprise financial and project accounting solutions and I'm always surprised at how this industry in general is more accepting of updates to software and upgrading in live with little to no process behind that. That's not to say nobody has a more rigorous process as you clearly experienced it, but it isn't as controlled, or as widely practiced, as my experience in other industries. 
 My main point was in response to what you actually posted before this more reasoned and entirely sensible observation. But I would still question how far back we ensure backward compatibility as I would also expect an organisation with these sort of processes to have a support contract and to not fall more than three years behind.

Trados Studio > 1. Trados Studio

Unable to open project package downloaded from a FTP Studio 2019

Top Replies