Hi Jerzy Czopik ,

I get the same error as you in Trados Studio 2022, 17.0.5.14757.

Anyway, I've managed to make it working splitting the file in 2 chunks (30k segments approx. each):

You can do the same as a workaround while this issue is fixed.

Maybe there is a limit in the number of segments?

I've found another issue:

Settings used to open before mentioned files:

But If I check also the Microsoft Excel 2007-2019 filetype (Bilingual checked and on top):

then the big file opens in Trados Studio, but without target content:

As if the regular Excel filetype were used, but it shouldn’t have been used as it is below the Bilingual filetype. I think RWS must have a look at this Bilingual filetype anyway.

Last, I’ve got a few out of memory errors while testing this.

Jesús Prieto 

Many thanks for taking your time to confirm, that the file does not open in S2022.

I've done something different—I copied only the source & target column into a new file, saved this under a new name and was able to open this very file in S2022 without any hassle, using Bilingual Excel.

My task consisted of creating paragraph-based TMs out of 15 Excel files for 15 language pairs. This works now using the new files, containing only source and target column, which is pretty enough for the task.

Using tab-delimited way via Olifant would have worked too, but then the TM would contain all content as plain text, while using Bilingual Excel allowed me to tag some unnecessary content.

Jesús Prieto 

Many thanks for taking your time to confirm, that the file does not open in S2022.

I've done something different—I copied only the source & target column into a new file, saved this under a new name and was able to open this very file in S2022 without any hassle, using Bilingual Excel.

My task consisted of creating paragraph-based TMs out of 15 Excel files for 15 language pairs. This works now using the new files, containing only source and target column, which is pretty enough for the task.

Using tab-delimited way via Olifant would have worked too, but then the TM would contain all content as plain text, while using Bilingual Excel allowed me to tag some unnecessary content.