Hello,

The error message you're encountering in Trados Studio is typically due to the software not being able to locate a file it needs. This can happen if the file has been moved, renamed, or deleted after it was initially linked in Trados Studio. Here's how you can resolve this issue:

Step 1: When the error message appears, click on the 'Browse' button. This will open a file explorer window.

Step 2: Navigate to the location where the file is currently saved. If you're unsure of the location, you can use the search function in your file explorer to find it.

Step 3: Once you've located the file, select it and click 'Open'. This will link the file back to Trados Studio.

Step 4: If the file has been deleted and you can't find it, you'll need to restore it from a backup if available. If not, you may need to recreate the file.

Step 5: To avoid this issue in the future, try to avoid moving, renaming, or deleting files that are linked in Trados Studio. If you need to make changes to these files, make sure to update the links in Trados Studio accordingly.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

RWS Community AI

HiMartine GUEBEL 

Yes, go to "File - Options - File types - SDLXLIFF - General" and increase the "Maximum embedded file size" to the maximum, which is 100.

Go from: 

to:

This will reduce the probability that the source file will not get embedded in the SDLXLIFF and that you need to locate it manually. If this happens in scenarios where you receive SDLXLIFF files from a third-party, ask them to make this change in their Studio client.

Thank you very much, Walter.

Hello! I am having the same problem described here. I work normally on a file in Studio (2024) from a package I received from the client and the target file cannot be created due to this issue. I set the file size to 1005 and I have never "move, renamed or deleted the files" anywhere, so I do not know why this happens and how to fix it. Can you help me, please?

Valeria Maria Tafel 

If you're working with a package it's likely the dependency file wasn't provided in the first place... in which case you have no solution other than to ask your client to provide it.  But do you really need to save the target file when working with a package for someone else?

Yes, because they want both the return package AND the signed Word file... it's a demanding client, but they pay well ;-))
Anyway, I have just managed to follow the procedure above and the issue seems resolved by selecting the sdlxliff file in the source package!
Is that contemplated?