Salesforce

WorldServer: WorldServer (WSXZ) package cannot be opened because one the sdlxliff files is empty and has 0 KB file size - 'Root element is missing' error

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Trados Studio
Symptoms/Context
When opening a WSXZ package exported from WorldServer an error message appears and the package cannot be opened. The error is:

Root element is missing

User-added image

This error can also be seen on Import back into WorldServer after translating in Studio.
Resolution
The root cause of this issue is that the files/tasks exported from WorldServer have an error when you open them in Browser Workbench and do a Save. The error means that these files cannot be generated as target files due to tag issues.

Once the issue is fixed in WorldServer, a new export should be done. If the export reports no error, the resulting WSXZ package will have no problems being opened in Trados Studio.

If this error is seen on Import back into WorldServer, the translator will need to verify they can successfully generate a new target file before creating a new return kit.

If your WSXZ package contains more than one SDLXLIFF file, as a temporary workaround, you could remove that empty SDLXLIFF from the WSXZ package and start working on the other files until the issue with the problematic Task is fixed in WorldServer.

To do so, follow these steps:
  1. Rename the *.WSXZ package to *.zip and extract it to a folder.
  2. Open the folder. You will notice that one of the SDLXLIFF files is empty.
  3. Remove that empty SDLXLIFF file.
  4. Zip the files and folders and rename the *.zip file to *.WSXZ.
  5. Open the WSXZ package in SDL Trados Studio 2021/2022 and perform your translation or review.
Root Cause
One or more SDLXLIFF files inside the package have file size 0 KB. The actual root cause could be misplaced tags in WorldServer that prevent the file to be saved, or a general corruption coming from a previous Return package import that failed with an error, but the error was ignored. The same error has appeared during the Export, but the translator has ignored it.
Reference
More details about the root cause and the resolution of this issue in WorldServer can be found in this article: 

WorldServer Save error 'Container not found'

Relevant article:

WorldServer - error at Save step after import of a Return package - "Root element is missing"
 
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by