Symptoms: When returning a fuzzy match segment from a translation memory that contains more tags than the original segment, the extra formatting tags are not removed from the translation. Explanation: The hotfix for CRQ-11178 introduced this issue. Resolution: Extra tags in the translation are now removed when returning a fuzzy match from the translation memory. SDL-hosted customers should contact SDL Support to...

Symptoms: When editing a segment in the browser-based editor in SDL TMS, these two characters, "<" and ">" , are not encoded correctly when the translation is saved. Instead of being stored using their encoded versions (&lt; and &gt;), they were being stored as literal characters. These characters would then be removed during the rebuild translation stage. Explanation: The browser-based...

Symptoms: Installing the security update for Microsoft Windows Server 2012 R2 (KB4338419, KB4338420) can prevent users from being able to access the SDL TMS user interface. Despite being able to log in normally, subsequent pages result in a server-side error. On some servers, the incompatibility is seen when starting the web site in which case the entire UI is inaccessible. Explanation: The security update is a remediation...

Symptoms: Switching the workflow for a task in SDL TMS could cause a "duplicate key" database error which would send the task to recovery. Explanation: This occurred due to a race condition on the database procedure responsible for switching the task workflow. Resolution: The procedure for switching the task workflow has been amended to ensure that it does not encounter a race condition during execution...

Symptoms: SDL Trados Studio packages downloaded from SDL TMS would sometimes have the wrong word counts in the fuzzy match bands when the package was opened in SDL Trados Studio. Explanation: This error occurred when the SDL TMS database query returned the fuzzy match band word counts in the wrong order. Resolution: The procedure for retrieving fuzzy band word counts has been amended to ensure that the counts are...

Symptoms: When editing an attribute, SDL TMS would sometimes stop responding and force a reboot of IIS in order to bring the website back online. Explanation: This occurred because editing an attribute also checked where that attribute might be in use. Attributes that are used extensively were returning a very large data set for the "in use" information, which was then causing the server to consume too much...

Symptoms: The status of jobs submitted to SDL TMS through the Adobe Experience Manager connector was not being correctly reported back to the connector after the job was created. Explanation: During job creation, SDL TMS was creating a temporary job as a placeholder. This temporary job was not being correctly processed and when the connector requested the status, the status of the temporary job was being returned. ...

Symptoms: Jobs previously created using the "Microsoft Word 2007-2013 (Studio)" file type in SDL TMS 11.4 were failing to successfully rebuild after the installation of the hotfix for CRQ-8612. Explanation: As above, the issue was caused by the hotfix for CRQ-8612 which inadvertently removed support for this deprecated file type. Resolution: Support for the deprecated file type is re-introduced by this hotfix...

We are pleased to announce the General Availability of SDL TMS 12.0 . This major version release delivers support for single sign-on with SDL ID as well as the first implementation of SDL Online Editor for SDL TMS . For more information, see the SDL Community post here . Don't forget the subscribe to this new area to receive update notifications.

Symptoms: Terminology entries containing ampersand characters were not being shown in the translation editor in SDL TMS even thought the exact term was present in the text for translation. Explanation: This issue was caused by a mismatch in how the ampersand character was being stored within the translation segment and in the terminology cache. Resolution: Terms containing ampersand characters are now stored consistently...

NOTE THAT THIS HOTFIX HAS BEEN WITHDRAWN. CUSTOMERS EXPERIENCING THIS ISSUE SHOULD INSTALL THE HOTFIX FOR CRQ-9346 INSTEAD. DETAILS OF THAT HOTFIX CAN BE FOUND IN THIS BLOG. Symptoms: Terminology entries containing ampersand characters were not being shown in the translation editor in SDL TMS even thought the exact term was present in the text for translation. Explanation: This issue was caused by a mismatch in how...

Symptoms: Some XLIFF 2.0 files were generating an error when trying to save the translated file and this caused the task to go to Recovery . Explanation: This issue was caused by an error in the XLIFF 2.0 filter which was not handling some special cases where the segment ended with a closing tag. Resolution: This hotfix deploys a new version of the XLIFF 2.0 filter which has the necessary fix to prevent the files...

Symptoms: Adding a Terminated workflow step to the workflow resulted in messages being written to the log file up to 100 times per second. As a consequence, disk space was being consumed rapidly and the performance of SDL TMS could degrade over time. Explanation: This issue was caused by not having an appropriate message handler for the Terminated message. Resolution: This hotfix adds a new message handler for the...

Symptoms: Downloading SDL Trados Studio packages from the Inbox View (Tasks) page in SDL TMS 11.4 could sometimes result in a ZIP file containing a single file with the name No_Files_Available.txt Explanation: This issue was introduced as part of a previous fix for CRQ-6656 which was incorrectly checking permissions and concluding that the user didn't have sufficient permission to download the selected tasks. ...

Symptoms: When using a custom Authorization step, tasks were being sent to Recovery. Explanation: This problem only happened when authorizing tasks from the authorization page in SDL TMS, but not when submitting tasks from a user's Inbox. The logic for authorization was not consistent between the two methods. Resolution: Both authorization actions, from the Inbox and from the authorization page, now follow consistent...

Symptoms: After multiple jobs had been created, some email messages were not being sent from SDL TMS . Explanation: The issue was caused by an incorrect deletion of email messages, occurring before the emails were sent to their recipients. Resolution: Unsent messages are no longer removed from the message queue in SDL TMS which will ensure correct delivery of these email messages. SDL-hosted customers should contact...

Symptoms: When a plug-in experienced a timeout in a multi-server environment, it was possible for two instances of the same plug-in to be running on two separate servers at the same time. Explanation: The issue occurred due to synchronization issues with the notification of the plug-in timeout. Resolution: Timeout notifications are now synchronized to prevent multiple instances of a single plug-in from running at...

We are pleased to announce the availability of a new hotfix for SDL TMS 11.4 which fully enables the integration between SDL TMS 11.4, SDL Trados Studio and TAUS DQF . Compatibility with V3 of the TAUS DQF API was first introduced in SDL TMS 11.3 and, after some feedback from early adopters, we have taken steps to improve on the original integration. Customers wishing to find out more about configuring SDL TMS 11.4...

Symptoms: After creating an attribute to use in a configuration, leaving both the Required Field box and the Hint Text field empty, the attribute is not displayed on the Edit Project Details page. Explanation: The issue occurred due to an error in the logic for displaying attributes on the Edit Project Details page. Resolution: We have now modified the page to retrieve the project information correctly and thus display...

Symptoms: SDL TMS would sometimes send tasks to Recovery at the Routing step because of database deadlocks. Explanation: This issue was caused by a custom workflow step which was changing the active workflow for many tasks concurrently. Consequently, this resulted in database deadlocks. Resolution: The stored procedure handling the setting of the active workflow has been optimized to eliminate the possibility of getting...

Symptoms: SDL TMS would sometimes become unresponsive due to high CPU usage by IIS when running the SDL TMS website. Explanation: This issue was found to be a result of multiple requests accessing the same resource concurrently, causing conflicts which could not be resolved. The only way to solve them was resetting IIS. Resolution: SDL TMS now manages requests to access the same resource to prevent conflicts and allows...

We are pleased to announce that SDL TMS Commute is now available on the SDL AppStore. SDL TMS Commute is a plug-in for SDL Trados Studio that provides access to SDL TMS inboxes and allows users to do translation and review without leaving their desktop SDL Trados Studio application. For more details, see the page on the AppStore here . Note that the SDL AppStore version of SDL TMS Commute replaces the one available in...

Symptoms: After installing SDL TMS 11.4, comments added on the Add Cost tab when editing a Job were not being retained once the page was submitted. Explanation: This issue was introduced in SDL TMS 11.4 as a result of some page optimizations to improve performance. Resolution: Comments added on the Add Cost tab are now correctly retained against the job. SDL-hosted customers should contact SDL Support to arrange...

Symptoms: After installing SDL TMS 11.4, word counting for jobs using Asian source languages changed, no longer using the previous character counting mechanism, but the new word-based tokenization. Explanation: This issue was introduced in SDL TMS 11.4 as a result of sharing new libraries with SDL Trados Studio, where the new word counting methodology was implemented. Resolution: The previous method of character counting...

Symptoms: After installing SDL TMS 11.4, it is no longer possible to re-assign the users for all tasks or to change the workflow step for all tasks on the re-assignment page. Explanation: This issue was introduced in SDL TMS 11.4 as a result of the changes made to differentiate between users and groups for systems with a large number of users. Resolution: Selecting a user or a workflow step using the selection boxes...