Message when opening (a file from) a package in Trados Studio: Dependency file not found

« Go Back


Article TypeSolution Article
Scope/EnvironmentTrados Studio

IMPORTANT: The update for Studio 2021 SR1 CU7 should have addressed most cases of such errors.
Now a Studio project package created from Studio CU7 or higher will always include the source if it was not embedded into the SDLXLIFF file.
This should eliminate such error messages. However: that does not apply to WorldServer packages.

You receive a Trados Studio project package or a WorldServer package and you open it in Trados Studio. The following message is displayed when you open one or more of the files in the package:

Dependency file not found: [SOURCE_FILE_NAME]
Original file before conversion.
Would you like to browse for this file?

User-added image

Here is another example of the error with a WorldServer package:

User-added image

Since the message points to a path and a file on the machine on which the package was created, and since that path is not accessible to you, you click No and start working on the translation.

However, when you want to use the real-time preview in your translation, or File > Save Target As to create your target file, you receive the same question as when you opened the package for the same document(s). Since the package does not necessarily contain the original source document, you cannot perform these interactive actions.


There are several ways to work around this issue.

If it is a source file issue where the source file (here called "Dependency File") needs to be embedded:

1. When the alert/error pops up, it is important to always click Yes and browse for the initial source file.

2. If the error happens when opening a WSXZ package exported from WorldServer and you have access to the WorldServer project, download the source file from there. On WorldServer, find the Task corresponding to the source file and click on More Options > Asset Options > Download to download the source file.

3. When browsing to the source file, use the option All Files to have all the files displayed, so that you can select the source file, as displayed here:

User-added image

The bilingual file will now open in the Editor view. Go to File > Save Target As and save the target file in exactly the same folder as the source.

If it is a Studio package issue...

If the first workaround fails, the bilingual file can be recreated by following the instructions presented in this article.

  1. You can ask the originator of the package to send you the original source file(s)
  2. The originator can add this file manually to the package before sending - of course, they need to be aware of this issue to know which source files to include.
  3. The originator can increase the embedding size so the files get embedded in the SDLXLIFF. This setting can be found in Tools > Options > File Types > SDL XLIFF > General > Embedding.

Although you cannot use Preview or Save Target As, this issue has no further impact on a normal project round-trip. Your return packages and translated files are not corrupted.

Important note for Norton users

If a project is left open in Trados Studio and Norton 360 performs an idle-time scan, it deletes some temporary files required for Studio projects. To solve this, open the Norton 360 dashboard, select Task scheduling and create an exception for the following folders:

  • C:\Users\%username%\AppData\Local\Temp
  • C:\Users\%username%\AppData\Local\Temp\SDLTempFileManager
  • C:\Users\%username%\AppData\Local\Temp\SDLTempFileRegen
Root Cause
This happens when the original source file is too large to be embedded in the SDLXLIFF file. Instead it is linked as a separate dependency file. When creating packages, these files are not automatically added to the package.

Development is aware of this issue and will provide a fix in a future release. Until this is available, follow one of the workarounds provided.
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by