Just found out that this issue has been introduced with CU02.

Rolled back our GS 2020 Test-Server to CU01 and these problems disappeared. 

Import works again, Reindex works fine but the TM update now again gives the error "Translation Provider threw exception", which should have been solved with CU02. Looks as if this fix introduced a new bug

Will now submit a support ticket.

Thank you Walter - yes a support ticket would be good. My theory is that a linguistic component might have slipped into GS CU2 that we were still able to fix for Studio CU6 but it was too late for CU2, but I am still validating that. It is the same issue as we were able to fix for CU6 - if you recall from the beta commiunity - and from what I have heard concerns de-ch, de-li, de-at, rm-ch but not de-de. It is a really odd one. A support ticket is the best way for us to track this from here. Thanks, Daniel

Hi Daniel

Ticket has been submitted. It is case # 502372.

And ... happy birthday¨
(sorry for the one day delay)

Hi Daniel

Your guess is correct. The "Input string .." issue when importing the TMX is related to the language code.
I changed the source language in the TMX from "De-CH" to "De-DE" and imported the file into the TM and .... the import runs flawlessly.

Regards
Walter

Yes - we have confirmed this also and are looking at options how we might provide a fix. Too early to say right now unfortunately but we are on it as it's very important. Thanks, Daniel

Hi all, can you please describe this problem in detail? We are just about to upgarde our test instances to CU2. 

thank you and regards,

Fana

Dear Daniel, could you please briefly describe the effects it would have if we - as Walter described - temporarily changed the language pairs? We are computer scientists, not translators, and I would have to be able to explain the effects of this possible workaround to the customer.

Hi Jan and all - I was on holidays but heard that the support team might have been able to help you in the meantime? Thanks, Daniel