Known issues

The following list details the limitations associated with Trados GroupShare 2020 SR1 CU9.

  • Support for SQL Server aliases might break after upgrading to GroupShare 2020 CU9. This is due to migrating a number of services to .NET 6.
  • The Translation Model Container database cannot be created when using SQL user for the connection between Trados GroupShareand SQL server. Since we don't recommend using SQL authentication for security reasons, there are no plans to address this in a future release. For more information, see Server security configuration recommendations (CRQ-30640)
  • When a language pair is added to an existing Trados GroupShare project from Studio, no project files are added for the new languages. This will be addressed with the next Trados Studio update. (LTGS-11782)
  • Finalized files are sometimes excluded from the Tasks report. (LTGS-11763)
  • Adding 'yyyy' as a Date & Time pattern to a new Language Resource rule fails with an 'invalid language resource data fortype DateTimeRecognizer' error message. (LTGS-11472)
  • MultiTerm Online: Opening termbases created with specific definition files fails with a NullPointerException error message. A potential workaround to this issue is to avoid having commas in the termbase name. (LTGS-11775)
  • Emoji-only segment cannot be saved in TM and show a 'empty target cannot be saved in the Translation Memory ' error. (LTGS-11787)
  • When running batch tasks on native files of a server-based project, the Upload and Check in files step fails to complete. (LTGS-11825)
  • Adding reference files from Trados Studio by using the Add Reference Files option results in an error when trying to check in. (LTGS-11830)
  • In the Reporting tab, sorting the Tasks table will not work or will order the tasks incorrectly. Contact support for a custom SQL script that improves this if needed. This will be addressed in future versions. (LTGS-11851)