When errors occur sending Translation Jobs, you can try the follow troubleshooting steps to solve the problem:
Important: Resending a Translation Job starts a new translation cycle and removes the connection between the Translation Job in Content Manager and the translation management system. Before you try Retry Sending, you must therefore delete existing Translation Jobs on the translation management system as these will be orphaned. Resending a Translation Job may also incur additional translation costs.
-
Item does not exist
- Problem: The item that was included in a Translation Job has since been deleted.
- Solution: Create a copy of the Translation Job, remove the deleted item, then Send To Translation.
-
Item does not contain translatable content
- Problem: If content is unintentionally not being included in a Translation Job, it may indicate you need to tweak your filtering.
- Solutions: There are several ways you can filter the content sent for translation:
- Check your
<ItemTypes> (in TranslationManager.xml) and ANL files (typically used for version of SDL TMS prior to version 2011 SP1)
- Check the translatable fields in Schemas (if your translation system support ITS)
- Check the Translate item options in Publication properties
- Check the Translation Job for duplicate items (if configured, items that are already In Translation are not sent—if you want to send these items again, create a Translation Job)
-
Item not valid according to its Schema
- Problem: The Schema of an item included in a Translation Job has since changed, rendering the item invalid.
- Solutions: Do one of the following, then click Retry Sending.
- Remove the item from the Translation Job
- Update the item to make it valid
- Roll back the Schema changes temporarily
-
Network connection
- Problem: Content Manager cannot connect to the translation system.
- Solution: Check your remote translation system is running by logging on to it directly. If it is up, wait a few minutes before Retry Sending; if it is down, contact your system administrator.
-
Timeout
- Problem: The connection times out when sending a Translation Job.
- Solutions: If you are experiencing timeout problems frequently, open the
TranslationManager.xml configuration file and adjust the following aggregation settings affecting server memory usage and database transaction time, then click Retry Sending:
<MaximumTridionItemsPerAggregatedTmsFile> specifies the number of SDL Tridion items that can be combined into a single file when sent to the translation system. If the value is exceeded, multiple files containing aggregated items are added to the Translation Job on the translation management system.
<MaximumTridionItemsPerTmsJob> specifies the maximum number of Content Manager items that can be combined into a single Translation Job on the translation system. If the value is exceeded, several jobs are created on the translation system for the single Translation Job on the Content Manager.