"Cannot find central directory"

expressisverbis wrote:

A few years ago, it happened something similar to me.
I couldn't open packages as well with Trados 2017. I can't remember any more of the exact error message, but I contacted the SDL staff at that time and they solved the problem.
Sometimes, closing and opening Trados works, a repair to the software, or an update (Windows or Trados Studio). Try to check if everything is okay.
But I would recommend you to get in touch with RWS community/staff for support.

https://gateway.sdl.com/CommunitySearchResults#gsc.tab=0

Joel Pina Diaz wrote:

Symptoms/Context

You receive a project package from a client, translator or reviewer with the extension *.sdlppx, *.sdlrpx, *.ttp, *.stppk or *.wsxz. When you open it in SDL Trados Studio, you encounter the following error:

An error occurred extracting the package. Cannot find central directory

Cannot find central directory

Resolution
Here are some workarounds that you could try:

Recreate the project package and send it again.
Check the WorldfServer project from which the WSXZ package has been exported and make sure all the source files have been correctly segmented and that they are not in error at the Save or Save target step. If there is not Save or Save target step after segmentation, open each file in Browser Workbench and do a Save to confirm that there is no error. You will most likely find the file/task that cannot be saved. This is the task/file that causes the error when exported to a WSXZ package. The error needs to be fixed and the the project should be re-exported to a new WSXZ package.
Add file extension exceptions to your AntiVirus/Firewall list. The extensions that need to be added are
*.sdlppx
*.sdlrpx
*.ttp
*.wsxz
*.stppk

Deactivate AntiVirus/Firewall suite protection before receiving a project package.
Instead of sending project packages via e-mail, put them on an FTP server or use a FileSharing Host and provide a download link.
Check if the download stream is not already in use because of other running downloads.

Root Cause
This behaviour/error might occur during the transfer of the project package. The behaviour is similar to problems that may occur with compressed *.zip, *.rar, *.7.zip etc. packages of known compressing tools like WinZip.

The corruption of SDL project packages can have several causes. The following list shows the common factors:

During project package creation, unexpected behaviour without notice causes corruption but the package is still created.
If the package comes from SDL WorldServer, one of the WorldServer project files might have not been segmented correctly or runs into an error when saved in Worldserver. If the error is ignored and the package is exported anyway, the corresponding sdlxliff file will be corrupted, causing the error
Slow download connection or a Internet connection that often disconnects during the project package download.
Project packages that are sent from a client via E-Mail but are first checked for any threatening content.
AntiVirus/Firewall suites that check files before, during or after the download and try to "repair" (in fact delete) package content.
AntiVirus/Firewall suites that include checks for E-Mail attachments and content or compressed packages, for example *.zip files and try to "repair" (in fact delete) package content.

James Plastow wrote:

I get a Central Directory error if I try to translate a Word document with a password in Trados. Perhaps your package has a Office document with a password? In which case you could convert the package to a zip file then remove the password.

Stepan Konev wrote:

You can unzip the package by renaming it first from the package extension to zip.
Then use its contents (sdlxliff, TM and TB if any) to create a new project. Then send the target sdlxliff file to your client. This will suffice.
Alternatively you can try to click the hyperlink that reads 'Base de conocimientos' to read their suggestions.