Import of TMX created in TransitNXT fails in Trados Go: "
TM task status: Failed. Task id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Question

Hello Community, We are currently trialling Trados Go, but are having issues uploading TMX files. We have created a TM for the language combination German (Switzerland) (source) > English (UK) (target) with the default Language Processing Rules and Field Template. Importing a test TMX with this language combination failed with the error: "TM task status: Failed. Task id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" (note that the Task id changes for every repeated attempt, e,g, xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx and xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) . No options are selected on the import page, and it is set to import all segments regardless of confirmation level. The TMX has been checked with TMXvalidator, and it is valid. The header info is:

The size of the TMX is 114KB, the number of segments is 75, and there are no segments with more than 2,000 characters. We have tried importing as a ZIP file, but that does not work either. It is not a general problem with importing TMXs, as we have created another TM with the same settings and successfully imported a different TMX (also created using the TransitNXT CAT tool) with the same language combination, but the content is a Word file aligned in the CAT tool. OS: Windows 10 22H2 Browser: Chrome Version 138.0.7204.158 Does anyone have any suggestions? Thank you for your help.

RWS Community AI · Accepted Answer

Probability score: 0.8 
 Question improvement suggestion: Provide the exact version of Trados Go you are using, as well as any specific error messages or codes that may appear during the import process. 
 In the meantime, based on the information you have provided, here is a suggested answer to your question: 
 Hello, 
 It seems you're encountering an issue with importing TMX files into Trados Go. Here are some steps and workarounds you can try to resolve the problem: 
 **Step 1: Validate the TMX File** 
 Even though you mentioned that the TMX file is valid according to TMXvalidator, double-check for any specific attributes or tags that might not be compatible with Trados Go. Ensure that the header information is correct and does not contain any typos. 
 **Step 2: Check for Missing Target Segments** 
 Open the TMX file in a text editor (like Notepad++) and search for translation units that have source segments but missing target segments. Remove any such translation units, as they can cause import failures. 
 **Step 3: Simplify the TMX File** 
 If the TMX file contains overly long translation units, consider cleaning it up by removing any segments that exceed a reasonable character limit (e.g., 5000 characters). This can help avoid performance issues during the import. 
 **Step 4: Use Workarounds** 
 - **Workaround 1:** Try importing the TMX file into Trados Studio first, then export it again and attempt to import the newly exported TMX file into Trados Go. 
 - **Workaround 2:** If you have access to Olifant, use it to open the TMX file and export it with the default style while unchecking options like "Export nodes" and "Export empty segments." 
 **Step 5: Check Language Codes** 
 Ensure that the language codes in the TMX file are valid and match what Trados Go expects. For example, replace any incorrect codes like EN-AUS with EN-AU. 
 **Step 6: Increase Server Timeout** 
 If you have control over the server settings, consider increasing the timeout settings in IIS for the TMService Farm to allow more time for the import process. 
 If these steps do not resolve the issue, please provide additional details about the specific error messages or codes you encounter during the import process, as this can help in diagnosing the problem further. 
 I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again. 
 RWS Community AI

Daniel Brockmann · Answer

Hi there Nigel - if at all possible, could you attach the ZIP file with the TMX inside here? I would then take a look. Transit TMX is known to be a bit tricky for import but perhaps I can find a straightforward solution. Thanks, Daniel

Daniel Brockmann
Team Trados @ RWS

Trados Cloud offerings > 2. Trados cloud offerings

Import of TMX created in TransitNXT fails in Trados Go: " TM task status: Failed. Task id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"