WorldServer - Error or unspecific message uploading Return package to WorldServer: 'Import Offline Work' 'No items were imported' or 'Null' or 'DocId not set' or 'Index 2 out of bounds for length 0'

Importing a WorldServer Return package results in the following message:
 

Import Offline Work

Found an XLIFF compatible file

The SDL Studio kit is being imported by the FTS Server. Please wait.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

The SDL Studio kit was imported successfully.

No items were imported.

Sometimes there is no message. You only see an unspecific message:

Import Offline Work
Ok

or just Null



Other possible error messages:

SDLWS:DocId not set!



Index 2 out of bounds for length 0.

When checking the ws.log for more information, you might find this error: 
 
 

To check if the Return package you are importing matches the project you are importing it into:

1- Rename the Return package to *.zip and extract it.
2- In the extracted folder, find the SDLXLIFF file and open it in Notepadd ++.
3- Search and find the file original= property and compare the path with the one of the project Tasks, especially the number before the project name. That number corresponds to the project group ID. Example:

file original= /work/TestProjects/24842_Test_project_name/Source-EN/Test_file-txt

If the path differs and the project group ID in the SDLXLIFF file is not the same as the one belonging to the project you are trying to import the Return package into, it means that the Return package contains a bilingual file that has been exported from a different project and this is why it cannot be imported in this project. Possibly, that project is already completed or cancelled.
Sometimes the path is the same, but the language is different. If that is the case, check the target-language= property. It might point to a different language than the one of the projects you are trying to import the Return package into,

Resolution 1: Do not import bilingual SDLXLIFF files belonging to canceled or completed tasks or projects, or created based on the source file. If the Return package contains a mixture of files related to active tasks and some related to canceled or completed tasks, remove the bilingual files related to canceled or completed tasks from the Return package and try again to import.

Resolution 2: If all the SDLXLIFF files included in the Return package do not match the project you are trying to import into, use the correct WSXZ package that was originally exported from the active project/task to create a correct Return package and upload it again to WorldServer. You might also run a new Export from WorldServer. Then Apply Perfect Match in Studio using the previous SDLXLIFF files. Finally, create a new Return Package and import it into WorldServer. More details about this workaround can be found in this article:

How to-retranslate the original Studio package using the "Apply Perfect Match" Batch using the damaged SDLXLIFF file from a Return package that cannot be imported in TMS or WorldServer

Resolution 3: related to error 'Index 2 out of bounds for length 0'. The translation needs to be re-done based on the exported package from WorldServer.

1- Re-export the project or Task to a new WSXZ package
2- Open the WSXZ package in Trados Studio
3- In Studio, Apply Perfect Match can be run, using the wrong SDLXLIFF file to retrieve the translation. Alternatively, a local TM based on the erroneous sdlxliff file can be created and applied to the WorldServer project created out of the original WSXZ package.
4- Once the project is translated in Studio, create a Return package and import it back to WorldServer.

1. Task no longer exists because it has been completed, cancelled or archived or it has moved to a step of which you are not the assignee. Sometimes the import fails even if only one of the bilingual files for import are related to canceled tasks while the others are for the correct active project.

2. One or more SDLXLIFF files in the Return package was not created from the originally exported WSXZ package. This can be determined by extracting the SDLXLIFF bilingual file from the return package, opening it in a text editor and verifying that the path to the source file contained in the file original= element matches the actual path on WorldServer. You will find a discrepancy.

3- Sometimes the file original value points to the translator's local computer. This is the case when error 'Index 2 out of bounds for length 0' appears. It means that the SDLXLIFF file in the Return package was most created locally by opening a source file and not by opening the WSXZ package. Such SDLXLIFF will not contain the reference to the WorldServer project and also other information included in the sdlxliff from the WSXZ package. Such file cannot be imported to a WorldServer project. That means that instead of working with the Export package, the translator downloaded the source file and opened it in SDL Trados Studio as a standalone file. By doing so, all the relevant metadata information coming from WorldServer are lost. Moreover: different segmentation might be applied. This procedure is incorrect and a user error.
 

This article might be relevant:

WorldServer - Error when importing/uploading Translation Kit as ZIP file after XLIFF export: 'Import Offline Work' 'No items were imported' and Value cannot be null. Parameter name: SDLWS:DocId not set!