Hi Vincent Roy,

Have you tried to import the TMX into a new file-based TM in Studio (2019 SR2 CU4 if possible)? If this works then try to export it again from the file-based TM and finally to import it again into your server-based TM.

Kind regards,
Nick

Hello Nick!
Yes we did try and unfortunately we get the same error. You can see it read/import the units but when it's done it shows this: 

Hi Vincent,
what I have done in similar cases:

- tested the other 2 import options, especially "imported data will be primarily used with presegmenteded legacy SDL Trados ITD or TTX files" once solved such a problem although we did not intend to use legacy files for translation

- checked the import option "Import translation units as plain text" - to verify if the issue comes from tags, or whether the whole TMX files is somehow corrupt. Using the plain text import would, of course, not be the preferred scenario because TM leverage would be negatively affected when you do not import the tags

- verify the TMX file in an XML or TMX editor

Good luck!

Kind regards

Christine

Hi Vincent Roy,

What happens if you try to import the TMX in GroupShare's web UI? If this also fails, do you have access to a GroupShare 2020 instance you could test it with?

Also do you happen to know the exact versions of Studio and WorldServer that the client is using?

Kind regards,
Nick

Hi Vincent Roy,

What happens if you try to import the TMX in GroupShare's web UI? If this also fails, do you have access to a GroupShare 2020 instance you could test it with?

Also do you happen to know the exact versions of Studio and WorldServer that the client is using?

Kind regards,
Nick