Exporting TU's when translation memory data file is corrupt

We have a SDLTM with some 65000 TU's which got corrupted.

Running integrity check on it reports a number of errors.

I did try to export the content and got the errors but stil some content is exported in to the TMX.

When I try to import that in the new SDLTM, only 58000 TU's get imported.

Is there a tool that would "ignore" the errors and export all valid TU's. 



Thank you

SImon

Screenshot of SDL Trados Studio error message during export. It reads 'Exporting translation memory to tmx file' with a warning 'One or more errors occurred.' Detailed error information is listed below.



Generated Image Alt-Text
[edited by: RWS Community AI at 12:33 PM (GMT 0) on 14 Nov 2024]
emoji
  • Hello Simon,

    I understand that you're having trouble with a corrupted SDLTM file. Here's a step-by-step guide to help you resolve this issue:

    Step 1: Download and install the SDLTM Repair tool from the RWS AppStore. This tool is designed to repair corrupted SDLTM files.

    Step 2: Run the SDLTM Repair tool on the corrupted SDLTM file. This should fix any errors and allow you to export all valid translation units (TUs).

    Step 3: If the SDLTM Repair tool doesn't resolve the issue, the problem might be with the Translation Memory Repository.xml file. This file lists all translation memories in the Translation Memories view. If it's corrupted, it can cause errors when opening TMs.

    Step 4: To fix a corrupted Translation Memory Repository.xml file, you'll need to locate the file and delete it. Don't worry, this won't delete your TMs. When you restart Trados Studio, it will automatically create a new, uncorrupted Translation Memory Repository.xml file.

    Step 5: After deleting the Translation Memory Repository.xml file, try opening your TMs again. If they open without errors, you should be able to export all valid TUs.

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

    Best regards,

    RWS Community AI

    emoji
  • From the suggested 5 steps, Translation Memory Repository.xml is not the culprit as the issue - is specific to the SDLTM. 
    I guess this was clear when I said that Integrity check (by SDLTM Repair Tool) reported issues.
    And also the problem is reproducible on several computers.

    SDLTM Repair was already used by my colleague and din't give any useful results or removed the error from showing up.
    The error being: "An error has occurred while using the translation provide NAMEOFTM: The translation memory data file is corrupt."

    emoji
  • Hello Simon,

    I understand that the SDLTM Repair tool didn't resolve the issue and the problem is reproducible on several computers. I'm sorry to hear that you're still experiencing this problem.

    Here's another approach you can try:

    Step 1: Create a new SDLTM file in Trados Studio.

    Step 2: Try to import the TMX file that you were able to export from the corrupted SDLTM into this new SDLTM.

    Step 3: If the import is successful, this new SDLTM should now contain all the valid TUs that could be recovered from the corrupted SDLTM.

    Step 4: If you still encounter errors during the import, it's possible that the TMX file itself has some corrupted entries. You might need to manually review and clean the TMX file before attempting to import it again.

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

    Best regards,

    RWS Community AI

    emoji
  • I guess I should lower my expectations towards the TradosAI. ;-)

    So i'm stil looking for method that will allow to export any recoverable TU even if without contect and fragment match data.

    Simon

    emoji
  • For the info, SDLTM Repair did great job. 

    It repaired the database and dropped only 49 out of 65942 TU's.  Great!

    We'll test this further but for the moment - SDLTM Repair is the tool I was looking for!


    emoji
  •  

    You might also find this article useful:

    https://multifarious.filkin.com/2023/01/29/tm-corruption/

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji