SDL TMS 2011 Service Pack 6 - Product Updates

SDL TMS 2011 SP6 | Service Pack 6 for SDL TMS 2011 (May 2015)

2016-05-08T13:29:00Z

We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 6. For comprehensive information on this release, please be sure to consult the attached Release Notes at the bottom of the page and the Knowledge Base articles referenced on this page.

As part of SDL’s strategy to deliver a consolidated localization ecosystem, we are pleased to announce that with this release, SDL TMS now supports SDL Trados Studio’s Language Resources Templates for SDL XLIFF-based Content Types, allowing to use the same set of segmentation rules, as explained in KB article 7837. In addition, SDL TMS now offers an option to apply the word count algorithms and TM match scoring using the same technology as SDL Trados Studio. Even though this Service Pack delivers a great step forward to align with SDL Trados Studio (2014 SP2), users may still experience some discrepancies. For a comprehensive explanation of the expected results when using this new option, we highly recommend you read KB article 7846. Finally, note that this release of SDL TMS has the same set of SDL XLIFF-based filters as SDL Trados Studio 2014 SP2 CU8. For more information, please refer to KB article 5375 and to the Release Notes.

In this release, SDL TMS introduces a new visual page showing graphical organizational data such as word counts, usage or top 10 most requested language pairs. This page enables at-a-glance understanding of the current system load and historical trending. For more information, please refer to the Release Notes.

This Service Pack provides users with an extension of the Audit Trail report to include records for changes performed on Content Types and Cost Matrices. For more information, please refer to the Release Notes and KB article 7964.

In order to improve performance, this version of SDL TMS no longer generates the legacy Trados 2007 translation memory format (.tmw) at TM export or Project TM creation.

Also, note that since the Studio package format is now largely adopted, the TMS Packages format has been removed from the Download options to eliminate confusion. Tasks downloaded as part of a TMS Package before upgrading to this SDL TMS version can still be uploaded back into SDL TMS in a return package without any problem.

Finally, we would like to draw your attention on the following articles announcing Legacy filters deprecation, implying the need to start switching to .sdlxliff-based Content Types in the upcoming months. For more information, please refer to:

For more details on this change and other changes and fixes implemented in this release, please refer to the Release Notes attached to this article.

NOTE: In this version of SDL TMS, the following browsers are officially supported:

Microsoft Internet Explorer® 9, 10, 11
Mozilla Firefox® 31 ESR

Please note that Microsoft Internet Explorer® 8 is no longer supported.
Compatibility Mode is NOT recommended. Using other browsers can result in some display or functionality issues.

Prerequisites

This release is available via an upgrade installer which will update your version of SDL TMS to the current release.
SDL TMS 2011 SP6 no longer supports Microsoft Windows Server® 2003. Nevertheless, it is now possible to use:

Microsoft SQL Server® 2008 Standard Edition (64-bit) R2 SP2 or SP3
Microsoft SQL Server® 2012 Standard Edition (64-bit)
Microsoft Windows Server® 2008 R2 Standard Edition
Microsoft Windows Server® 2012 Standard Edition

Installation and upgrade process:

Customers interested in upgrading to SDL TMS 2011 SP6 are encouraged to contact SDL Support to coordinate the assistance with pre-upgrade planning, custom component review and validation and upgrade execution and validation. If you have a Support and Maintenance contract with SDL, you can access SDL Support at the SDL Gateway.

This upgrade will restart the web server (IIS) and all SDL TMS services, so a short window of server downtime will be required. If you are installing on a multi-server environment, the database operations will only be performed during the installation on the first server.
You are advised to refresh your browser cache after every SDL TMS upgrade.
Follow the SDL TMS 2011 Installation Guide. A copy is available within the ISO file.
The installation ISO image is available at: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6.

SDL TMS 2011 SP6 CU1 + SDL TMS 11.0 | Impossible to download files from SDL TMS

2016-01-27T14:02:00Z

Symptoms:
In some cases, when source files have been uploaded to SDL TMS in a .ZIP file of nested folders, it was not possible to download those files from the Job's Items and the Task Status Summarypages or from the Online Translation Interface page.

Explanation:
The issue was caused by a restriction of 4 parameters, implying a four-folder structure for the source file's path. For example, a valid path would be like this: JobId\SRC\Language\fileName.
If the path for the source file contained more than four folders, namely additional sub-folders, then the user could not download the requested files.
This would typically happen when the uploaded source file implied a .ZIP archive containing a folder structure generating too many unsupported sub-folders (for example: ...\ JobId\SRC\Language\folder1\folder2\fileName).

Resolution:
The solution lifts this folder structure limitation.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Note that this hotfix is delivered for two different versions of SDL TMS, therefore, depending on the current installation, customers who host SDL TMS themselves should download one of the following installers:

If the TMS instance is running TMS 11.0, then download SDLTMS11.0 Hotfix for TMS-8653.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/11.0/Hotfix.,
or

If the TMS instance is running TMS 2011 SP6 CU1, then download SDLTMS2011SP6CU1 Hotfix for TMS-8653.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

Note:
The Microsoft file path length limitation still applies.

SDL TMS 2011 SP6 CU1 | SDL XLIFF files sent to Recovery at Apply TM stage

2015-11-06T14:12:00Z

Symptoms:
If a match has duplicate tag IDs in the translation memory, applying it during the ApplyTM stage sends the task to Recovery with this information in the logs “An item with the same key has already been added.”

Explanation:
SDL TMS consumes a specific external Component responsible for sorting the TM candidates matching, based on criteria such as score, last modified date and usage count. As this Component has recently changed, the existing integration in SDL TMS was no longer fully valid and was therefore sending tasks to Recovery in situations like the scenario mentioned above.

Resolution:
The fix rectifies the integration so that tasks are no longer sent to Recovery.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS2011SP6 Hotfix for TMS-5211.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

Note:
Pre-requisite: "SDLTMS 2011 SP6 CU1 - Hotfix for TMS-7375, TMS-6525 and Tech Preview for MS Word 2007-2016 PPT" available in this post.

SDL TMS 2011 SP6 CU1 | Impossible to retrieve Configuration details for integrations using the Java CTA

2015-10-19T13:16:00Z

Symptoms:
For a Configuration in use within a Project, it is impossible to retrieve the Configuration's details from third-party applications that use the Java Content Transfer API (CTA), therefore preventing the integration from working.

Explanation:
When a user needs to create a job request from a third-party application, using CTA, a request is sent to SDL TMS to get the Configuration's details. An issue was identified in the serialization of the Configuration's response when the response contains a Project node (indicating that the Configuration is in use in a Project).

Resolution:
The fix allows a proper reading of the XML response and Configuration details can now be retrieved correctly.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host SDL TMS themselves should download and use the updated installer for sdl.tms.cta.jar from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | External Machine Translation queue blocked for Legacy Content Types

2015-10-15T13:18:00Z

Symptoms:
In some cases for Legacy Content Types, tasks coming from an External Machine Translation (EMT) Engine for processing get stuck in the EMT queue.

Explanation:
When matches are returned from the EMT Engine, the ITD bilingual file needs to be rebuilt. Sometimes SDLX would crash due to a buffer overflow, leading then to an access violation. This would block the rebuild of the affected ITD file, preventing the next tasks in the queue from being processed and consequently, blocking the EMT processing entirely.

Resolution:
This fix prevents SDLX from crashing and, in case other issues occur, it also offers an improved logic of processing tasks in the EMT queue. The tasks that are received from the EMT engine and are ready to be rebuilt are now given priority, being followed by the tasks that are ready to be sent to the EMT Engine.

Additionally, as this issue concerns the pre-processing area, be aware that the fix contains the "Microsoft Word 2007-2016 (Tech Preview) - Pre-processing tool available for SDL TMS 2011 SP6 CU1" as described in this post. Therefore, implementations that already have installed this Pre-Processing Tool will not have it removed by accident.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS2011SP6 Hotfix for TMS-7375.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | Microsoft Word 2007-2016 (Tech Preview) - Pre-processing tool available for SDL TMS 2011 SP6 CU1

2015-10-09T13:19:00Z

Symptoms:
To answer growing demands of supporting more features, as well as Google Docs and Libre Office 4, a new Microsoft® Word 2007-2016 File Type (Tech Preview) has been made available.

As the SDL TMS user community is also a large consumer of these file types and of SDL Trados Studio, we are happy to announce the availability of this File Type Tech Preview (delivered in June 2015 by SDL Trados Studio) in a new Pre-Processing Tool available for SDL TMS SP6 CU1 users.

Explanation:
We recommend that users have SDL Trados Studio 2015 (June 2015) with SDL TMS 2011 SP6 CU1, as the set of filters is the same.

For now, the version of the Microsoft® Word 2007-2016 File Type delivered in this article matches the SDL Trados Studio 2015 release notes, available in KB article 8571. There is no corresponding out-of-the-box Content Type in SDL TMS SP6 CU1, but there is a new Pre-Processing Tool made available for users who want to start adopting the filter from its early stages.

Note that the production-ready version of this file type will be delivered with Studio 2015 Service Release 1. Consequently, the next release of SDL TMS will update the filter available in the Pre-Processing Tool with the latest changes available and expose the matching out-of-the-box Content Type.

Resolution:
SDL-hosted customers should contact SDL Support to arrange for this new functionality to be deployed.

Customers who host SDL TMS themselves should download the installer for SDLTMS2011SP6CU1 MS Word 2007-2016 Preprocessing Tool Tech Preview.exe from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | Missing format painting coming from Machine Translation prevents translations' inclusion in the ITD

2015-10-06T13:19:00Z

Symptoms:
When the format painting is broken or missing, the ITD is prevented from being rebuilt. Consequently, the content from the matches from the Machine Translation engine are reverted in the SDL TMS database and therefore they are not included in the ITD file.

Explanation:
After matches are returned from the Machine Translation engine, they are transferred into the ITD file. If the format painting is broken, this transfer cannot happen. The merge mechanism is not tolerant of missing format painting and as a result, the changes coming from the Machine Translation engine are rolled back.

Resolution:
The fix makes SDL TMS more tolerant for format painting mismatching and therefore matches from the Machine Translation engine are kept.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host TMS themselves should download the installer for SDLTMS2011SP6 Hotfix for TMS-5198.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | ERRATUM for TMS-6026 for SDL TMS 2011 SP6 CU1

2015-10-01T13:20:00Z

Symptoms:
There were issues identified after delivering the hotfix from "8680: Hotfix for defect TMS-6026 for SDL TMS 2011 SP6 CU1" with Microsoft® Internet Explorer 11 (IE 11) users who could no longer use the downloading and submitting functionalities from the Inbox.

Explanation:
In a minor version of Internet Explorer 11, namely 11.0.23, Microsoft has introduced the "Edge (Default)" mode which is not supported by SDL TMS 2011 SP6 CU1.

Resolution:
This new fix reverts the initial hotfix and provides a resolution for the issue raised with TMS-6026 (see this post). The issue was that the PerfectMatch tab in the Create Job page was not showing any candidates when using IE 11. SDL TMS now uses the wgxpath library, allowing usage of XPath to retrieve PerfectMatch candidates.
If the hotfix for TMS-6026 was not applied, applying this new installer will fix the PerfectMatch candidate list.

SDL-hosted customers should contact SDL Support to arrange for this rollback to be applied.

Customers who host TMS themselves should download SDLTMS2011SP6 Hotfix for TMS-7372.exe from the following FTP site:ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | View Job permission granted in child Group is not effective in the user's main TMS Inbox

2015-09-30T13:20:00Z

Symptoms:
You are a user created in Organization A, which is parent-organization to Organization B. You have the "View Job" permission granted for Organization B. When navigating to Home > Inbox , without selecting a specific organization in the navigation tree, you can see jobs from Organization B, but no link is available to get to the Job Summary page.

Note that when you select the child-organization from the navigation tree, going to Home > Inbox > Organization B, the job links are displayed fine and work as expected.

Explanation:
The mechanism that checks the permissions for the main Inbox page was faulty and only checked permissions for the Organization the user was created in.

Resolution:
The solution now fixes this issue and checks permissions for each Organization present in the Inbox.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host TMS themselves should download the installer for SDLTMS2011SP6 Hotfix for TMS-7132.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | Bad detection of IE 11 prevents some functionalities in SDL TMS from working properly

2015-09-09T13:22:00Z

Symptoms:
Using Microsoft® Internet Explorer 11 (IE 11) does not work for some functionalities in SDL TMS, for example, selecting Jobs for PerfectMatch on the Job Creation portal.

Explanation:
The way to handle the browser detection for IE 11 has become obsolete, not allowing an appropriate identification of the browser. This in turn did not permit the rendering of some data in SDL TMS.

Resolution:
The fix provides an up-to-date method of handling browser detection, which now allows better data rendering in IE 11.

As this fix generated issues for IE 11 with Edge as default mode - see this post - the installer for SDLTMS2011SP6 Hotfix for TMS-6026.exe has been removed from the FTP site.

SDL TMS 2011 SP6 CU1 | SDL Nexus Service failing to validate a safebyte license key

2015-09-02T13:23:00Z

Symptoms:
When using SDL Nexus Service with FTP configurations a SfbLicenseException error in the Event log may be displayed indicating that the license validation failed:

The license key is invalid or has been deactivated. Please contact ComponentForge Sales Team at sales@componentforge.net.

Explanation:
This happens when the license for the third-party component used to establish the FTP connections has expired.

Resolution:
Uninstall SDL Nexus Service and install the latest version available as per description below.

There is no need to reconfigure SDL Nexus Service after the upgrade.

SDL-hosted customers should contact SDL Support to arrange for this new version of SDL Nexus Service to be deployed.

Customers who host TMS themselves should download the installer for Sdl.Nexus.msi from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | The SDL Buddy error page is displayed when accessing reports in SDL TMS

2015-08-28T13:23:00Z

Symptoms:
When navigating to the Reports area in SDL TMS, sometimes after selecting the report to be run, an SDL Buddy error page was displayed. This prevented the user from drawing reports.

Explanation:
The issue happened in some cases due to a change in how the state of the report's format type is stored in the user session.

Resolution:
The fix addresses the error and reports can be drawn without any issue.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host TMS themselves should download the installer for SDLTMS2011SP6CU1 Hotfix for TMS-6924.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1/Hotfix.

SDL TMS 2011 SP6 CU1 | Cumulative Update 1 for SDL TMS 2011 SP6 (August 2015)

2015-08-21T13:24:00Z

We are pleased to announce the release of SDL Translation Management System 2011 Service Pack 6 Cumulative Update 1. For comprehensive information on this release, please make sure to consult the Release Notes and other materials attached to this article, as well as the Knowledge Base articles referenced on this page.

Customer Satisfaction:
One of the major focuses of this release lies in defect fixing, delivering about 40 fixes in areas such as:

File Processing to enable better support of Content Types
Group Permissions to reinforce security
Reporting - to increase performance and more accurate data retrieval
User Interface improvements and better character support to enable easier downloads
System performance.

Language Processing Technology & Integrations:
To continue delivering on the strategic goal of consolidating the SDL technology stack for language processing, SDL TMS 2011 SP6 CU1 includes updates in the following areas:

SDLXLIFF filter update
Support for MultiTerm Server 2015 as a terminology provider
Extensions to cross-product language support
Application of Studio-style to real-time TM Lookup in the TI
User-requested enhancements for the GroupShare integration
Improved performance using the TMS TM provider in SDL Trados Studio (Studio)

Additional New Features:
In this release, we continue building on the platform of prior releases in the following areas:

A new Login page with improved security
An extension to the CTA to add integration jobs to a TMS Project
A Pseudo-translation tool for round-tripping content without human intervention

Related KB articles for this release:

KB article 8329: TMS API key (ex-TM lookup API) tied to "Use TMS API" Group Permission
KB article 8393: Which version of SDL Trados Studio to use with SDL TMS 2011 SP6 CU1
KB article 8438: Using the SDL TMS Pseudo-translate MT Provider
KB article 8410: Increased Language Compatibility between SDL TMS and Studio.

Installation and upgrade process:

This upgrade will restart the web server (IIS) and all SDL TMS services, therefore a short window of server downtime will be required. If you are installing on a multi-server environment, the database operations will only be performed during the installation on the first server.
You are advised to refresh your browser cache after every SDL TMS upgrade.
Follow the SDL TMS 2011 Installation Guide. A copy is available within the ISO file.
The installation ISO image is available at: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/CU1.

SDL TMS 2011 SP6 | Hotfix for defect TMS-3058 - Job Cost information

2015-08-07T13:26:00Z

Symptoms:
Within the stages of a workflow in SDL TMS, costs are only updated at the Pre-processing and Update Invoice stages. Even if dynamic cost variables are added or updated between these stages, the job cost in SDL TMS is not updated. SDL TMS solves this limitation by calculating job costs ‘on demand’ whenever it receives a request to display this information through the user interface.

SDL TMS should take a fresh snapshot of the costs after any scenario in which a job cost can change, for example, when editing a job (by adding/updating dynamic cost variables) or when a task is terminated or authorized.

Explanation:
SDL TMS would not re-cache the recalculated data, after a user had edited the cost from the Job page and therefore it would not render the correct information on the Job Summary page and Reports (Job Quote, Job Invoice, Project Invoice).

Resolution:
Cost changes are now reflected correctly in Reports and the Job Summary page.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host TMS themselves should download the installer for SDLTMS2011SP6 Hotfix for TMS-3058.exe from the following FTP site: ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/Hotfix.

SDL TMS 2011 SP6 | Entities wrongly converted by SDL TMS after segments are received from the BeGlobal machine translation stage

2015-08-07T13:25:00Z

Symptoms:
When SDL TMS receives matched segments containing one of these 3 character entities < , > or & from SDL BeGlobal, SDL TMS escapes the returned characters, therefore displaying incorrect characters.

For example, the string: "This is a document with a <1> placeholder" gets displayed as: "Este es un documento con un < 1> marcador".

Explanation:
SDL TMS was operating a double escaping of the above mentioned characters at different points along the Machine Translation flow.

For example, the ampersand character would be first "XML-escaped" to represent a &, which is fine, but this would then be re-escaped to display &.

Resolution:
SDL TMS now respects the returned characters and no longer attempts any incorrect escaping.

SDL-hosted customers should contact SDL Support to arrange for a hotfix to be deployed.

Customers who host SDL TMS themselves should do one of the following:

if you are using SDL TMS 2011 SP6, you need to download and install SDLTMS2011SP6 Hotfix for TMS-5695.exe from the following FTP site:
ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP6/Hotfix.
if your are using SDL TMS 2011 SP5 CU2, download and install SDLTMS2011SP5CU2 Hotfix for TMS-5695.exe from the following FTP site:
ftp://sdlpatches:5dlpatch35@ftp-emea.sdlproducts.com/SDL TMS/2011 SP5/CU2/Hotfix.