Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
We face severe issues since the upgrade of GS 2020 to CU2.
TM Update tasks launched from within Studio all fail with the error message "An error occurred while using the translation provider ....".
TMs cannot be reindexed, they all fail with the very meaning ful error message "One or more errors occurred" when started through the GS web management interface. When started from Studio, Studio will say that the reindex worked fine, but the task fails on the server with the same error.
We then tried to recreate some of these TMs but even this won't work: we can export the TMs fine to TMX, but when we try to import them into a new TM, the import fails with the error message "Input string was not in a correct format".
We then tried to create a new TM on another GS server (also GS 2020 CU2) and get the same error. We cannot even import the TMX files, the import fails with the same error "Input string was not in a correct format".
Is anyone else facing comparable issues?
Ticket has been submitted. It is case # 502372.
And ... happy birthday¨ (sorry for the one day delay)
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…
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
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
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.
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,
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