Tips

The fascinating TV show about Trados Studio errors continues!

The Error occurred in file ... Attempted to divide by zero error appears when you try to import a WSXZ package. The error is rare: Google knows about it by hearsay, and even if you use the link, you will find the description of termbase issues, but the real reason turned out to be different.

The exact origin this issue is unknown, but it is related to some problems with the XLF file structure. Surprisingly, the problematic XLF file itself gets opened as intended (in our case).

First, you should inform your client about the issue. If the client is unavailable or has no idea about how to solve it, perform the operations below. Their common purpose is to retrieve the XLF file from the package and translate it separately. The order of actions is as follows:

• Rename the package file: replace the WSXZ extension with ZIP or just add the ZIP extension.
• Unzip the resulting ZIP archive.
• Manually create a project in Trados Studio with the name repeating the name of the source package and the same language direction.
• Specify the XLF file from the unzipped archive as a file for translation.
• In the project, create an empty translation memory and import the TMX file from the unzipped archive into it.
• If the unzipped archive contains a TBX file, connect it as a termbase. You need to convert it from TBX to SDLTB first—we will tell you how to do it in one of the future posts because this one is already getting huge :)
• Namely, translate the project as usual.
• Put the translated XLF file instead of the XLF file with the same name into the unzipped archive without changing its structure.
• Make an archive out of the unzipped ZIP archive.
• Change the ZIP extension back to WSXZ. Then, you will probably have to either upload the package to SDL WorldServer (if you have done everything correctly, the server will accept it) or send it to your client, depending on your procedures.
• Profit.

The instruction seems long, but it takes actually longer to write than do what it tells: it is important to understand the purpose of each action though. And if your XLF file is small and the translation memory does not reduce the amount of work, you can translate it by opening in Trados Studio directly, i.e., even without creating a project.

If you know a more humane method, please share.

Sometimes, Trados Studio gives a mysterious message while importing a package:

Given that, it doesn’t import the package, the project doesn’t appear in the list, and it is impossible to work. At the same time, the System Volume Information folder is in the drive indeed, but it is hidden, and who knows how it is connected with Trados Studio projects.

It is not entirely clear what causes this error; however, it’s quite easy to fix:

• Close Trados Studio.
• Delete the UserSettings.xml file in the Trados Studio folder. It is usually located in the c:\Users\[USER NAME]\AppData\Roaming\SDL\SDL Trados Studio\[Trados Studio version] folder.
• Start Trados Studio.
• Re-import the package.

This method works in Trados Studio 2015 and 2017, but it has to work in other versions too.

Trados Studio is a source of numerous errors, which sometimes turn out to be quite exotic. Troubleshooting methods are [or should be] described in the help section of the SDL portal. Many of them are gathered by hashtag #tradosstudio on our website.

If you encounter a mysterious error, try checking the main trouble spots before diving into help sections and forums. The general method for removing puzzling errors in Trados Studio elaborated in the process of suffering lots of bumps and bruises looks like as follows:

• Check that the general length of the path to the SDLXLIFF files of the project is not too big. The total length should not exceed 255 symbols.
• Check that the names of the folders and files do not contain symbols that are not inherent to the languages you usually work with (hieroglyphs, letters of RTL languages, all kinds of letters with superciliary and suprailiac dashes, circles, etc.). Studio is suspicious of them. For example, the The specified project name is invalid. The name should not contain any invalid characters such as: \ / : * ? " < > | error is caused by the presence of Cyrillic symbols with wrong character encoding in the project name.
• Check that the project files, particularly SDLXLIFF and SDLTM, are not flying in the air, i.e., are not in the standard folders of Dropbox, Google Drive, etc. When you work directly from the cloud, any change of the file will make Trados Studio and the local cloud application fight to be the first to process it, and the translation process will suffer.
• Check the state of the working translation memory (TM) in the imported package:
• it must be present—sometimes users simply forget to add it;
• it must be active—the corresponding checkbox in the project settings must be checked;
• the language direction of the TM must match that of the current SDLXLIFF file;
• the translation memory file (SDLTM) must not have the Read Only attribute, and in the case of the online memory, a connection to the server must be established.
• Repeat this for the termbase.

* * *

If it doesn’t help, try looking for the cause of the error with the help of an exact search through the text of the error message.

If you use WordFast Pro 5.6 or another version older than Wordfast Pro 5.12 and try opening TXLF files generated in the new version, you may get the following error message:

Attribute ‘gs4tr:uuid’ is not allowed to appear in element ‘file’

It takes place because earlier WF versions can’t recognize this attribute. To solve this problem, you can download and install a new 5.12 version. But there is another bypass solution.

Open the TXLF file in the text editor Notepad++, use the search function (CTRL+F) to find “gs4tr:uuid,” and delete the attribute together with its number and the redundant space as shown in the screenshot. Click the Save button and close the file tab.

After this, the file opens in WordFast 5.6, and no error messages appear.

The error message looks like this:

The message The requested data file could not be located appears when one is trying to start Trados Studio. It is extremely laconic: what file exactly she lacks, where it must be located, why she needs it—who knows.

This problem can occur in any version of Trados Studio, even 2021, usually after the upgrade installation. SDL states that they have already fixed this in Trados Studio 2021 SR1.

To get rid of this error:

1. Close Trados Studio (if you have miraculously managed to start it).

2. Search the hard drive for the following folder:

— if you have Trados Studio 2017:
C:Users\%UserName%AppDataLocalSDLSDL Trados Studio14.0.0.0

— if you have Trados Studio 2019:
C:Users\%UserName%AppDataLocalSDLSDL Trados Studio15.0.0.0

— if you have Trados Studio 2021:
C:Users\%UserName%AppDataLocalSDLSDL Trados StudioStudio16

3. In that folder, find the file TranslationMemoryRepository.xml. That is the file Trados Studio was lacking and was too shy to provide its name. You can simply delete it, but you will want to save it just to be safe. The easiest way is to rename it by adding another extension to its name: TranslationMemoryRepository.xml.old.

4. Start Trados Studio. When starting, it must create another file with this name and work normally.

* * *

The process is described in details here.

One of the amazing errors in Trados Studio sometimes occurs when you try to save translation—i.e. after you press the CTRL + S key combination. It looks like this:

To a non-specialist, this message yields little information. To be more precise, it is meaningless—one just doesn’t have a clue. Moreover, Trados Studio doesn’t allow saving files, and it seems to you that the results of your work are lost.

Hold your horses and don’t import the Trados Studio package again! If you do this, the results of your work will be lost indeed.

According to our experience, this error only occurs when several package files have been opened simultaneously with the Include subfolders flag set:

The way out is to open files one by one, not “in bulk.” In this case, Trados Studio saves the changes “properly.”

Thus, if you face this error, the algorithm of saving the performed translation is as follows:

• Close the files without changing them (actually, you don’t have another option at this stage).
• Remove the Include subfolders flag.
• Open the documents one by one, fill the target with your translation from the translation memory by replacing the existing translation, if there is one, with it using the CTRL + T key combination. (You have been confirming segments through CTRL + ENTER while translating, haven’t you? We hope you have; otherwise, this method won’t work.)
• Save the documents the usual way—by pressing CTRL + S.