Resolved issues in Translation Manager 2.0 SP1
This section describes the issues that were fixed in the 2.0 SP1 release of Translation Manager.
- Deleted items in Translation Job
- When an item that was sent for translation in a Translation Job was deleted, the Translation Job would remain in the In Translation state. The Translation Job is now set to the Error retrieving state allowing you to cancel the Translation Job.
- Creation of multiple versions of items
- Translation Manager 2.0 would create multiple versions of items when errors occurred and when sending an item to translation the checkout/checkin logic would create an extra copy of the content as it was when the translation was sent.
- Log file creation and size
- In Translation Manager 2.0 several log file were created and it was not possible to set a size limit of these files. In Translation Manager 2.0 SP1, one log file is created each day.
- Translation Jobs sent to non-existent configuration
- Translation Manager 2.0 would create multiple versions of items when errors occurred and when sending an item to translation the checkout/checkin logic would create an extra copy of the content as it was when the translation was sent.
- Inconsistent Translation Job states
-
A single Translation Job in SDL Tridion is split into several jobs in SDL TMS in two situations: when the items it contains exceeds the specified Job size, or when you create a Push Translation Job to several targets. In Translation Manager 2.0:
- in the first situation, if one of the SDL TMS jobs was canceled (deleted, terminated, and so on) and others were successfully completed, the Translation Job in SDL Tridion was set to Canceled
- in the second situation, if one of the jobs was canceled and another completed, the Translation Job in SDL Tridion was set to Completed
- Disconnected database connection
- When a database connection got disconnected, the Translation Manager Service did not reconnect. The Translation Manager Service will now recreate the connection on a regular basis (each time it comes out of a wait cycle).
- Leaked database connections
- The connection pool used by the COM+ application could previously run full under heavy load, resulting in a timeout expired error message being logged every time the service tried to get an item from the queue. This may have occurred because all pooled connections were in use and max pool size was reached.
- Translating Keywords in Components
- When you sent a Component that contains Keyword fields for translation, the Keywords fields were translated (if not done so already) but the translated content was stripped when returned to the Content Manager.
- Checking in and unlocalizing canceled items
- The first time a SDL Tridion item is sent for translation, the item is localized and checked out. In Translation Manager 2.0, if the SDL TMS job was cancelled the items in the job were checked in but not unlocalized. In Translation Manager 2.0 SP1, these items will now be unlocalized.
- Translation Manager Service starting the COM+ application
- When you sent a Component that contains Keyword fields for translation, the Keywords fields were translated (if not done so already) but the translated content was stripped when returned to the Content Manager.