Salesforce

WorldServer: Error 'Could not find a part of the path' when importing a Return package or saving a file in Browser Workbench after a failed import

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer
Symptoms/Context
When attempting to save a file in Browser Workbench or during the import of a Return package, you get this error message:

An error occurred while saving the asset into AIS. Details: com.idiominc.wssdk.asset.WSAssetSegmentationException: Could not find a part of the path

The path indicated in the error points to the WorldServer application server. If it points to a local computer, please refer to this article:

WorldServer - Error 'Could not find a part of the path' when importing a Return package, saving a file in Browser Workbench after an import or at the next Save step. The path indicated in the error points to a local computer directory
Resolution
The resolution needs to be applied in Trados Studio.

The error message when opening such a bilingual file in Studio in these cases will contain a reference to user’s machine temp folder where the file was. When opening the file included in the Studio Return package, this error/alert appears. This is the same error that appears in Browser Workbench during the Save action after the import.

To prevent the error, the translator working in Trados Studio should always make sure to select Yes when prompted for a dependency file and embed the source file. If the translator ignores the warning and does not embed the source file, no target file will be created in Trados Studio, an error will appear when importing the Return package and the same error will also appear at the next Save step in the workflow on WorldServer.

What should *always* be done in this case is to:

1- Retrieve the source file from WorldServer 
2- Open the WorldServer package or – if you have only the Studio Return package – rename the Studio Return package to *.zip, unzip it and open the SDLXLIFF file in SDL Trados Studio. If you do not have a WorldServer package, export it from WorldServer.
3- On open, the error message about missing dependency file (the source file is meant) will be prompted with the option to select it now 

User-added image

4- Choose YES to select and navigate and open the corresponding source file (select All files in the Open Dialog if you cannot see the source file in the folder where it is stored)

User-added image

5- Perform your translation normally and in Studio, go to File/Save to save the bilingual SDLXLIFF file.
6- If you have worked with a WorldServer Studio package, create your Return package normally. After the upload/import of the fixed file in WorldServer, the Save action in Browser Workbench will work without error. If the Task is in autoerror at Save, complete the Autoerror.
7- To create a fixed Studio Return package based on a Studio SDLXLIFF file, find the Studio file you have opened and saved in Studio, zip it and then rename the extension to *.wsxz. Then upload it again to WorldServer. After the upload/import of the fixed file in WorldServer, the Save action in Browser Workbench will work without error. If the Task is in autoerror at Save, complete the Autoerror.
 
Root Cause

When a WSXZ package is processed in Trados Studio, it may occur that the embedded dependency file is removed from the bilingual file, e.g. while the bilingual file is open in Studio Editor the corresponding dependency file from the temp folder of user’s machine is removed. This happens often when the translator ignored the warning about the Dependency file when opening the project file in Trados Studio.
 

As a result, the Return package will not be imported into WorldServer. The translator or user who performs the upload will receive an error. If the user ignores the error and completes the Translate step, once the Task reaches a Save or Save target step or is opened in browser workbench and a Save is done, the error will occur.

Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by