Isolate translation problems

Procedure To isolate the application that is causing the translation failure, run the translator in different contexts: Run the translator in a standalone mode from the command line. For information about running the translator from the command line, see the translator documentation. It the translator fails, it is a translator issue. See the translator documentation for information about fixing it. If the translator works, go to the next step. Perform a translation within the context of Dispatcher Server using the administration client. If the translation fails, it is a Dispatcher Server issue. If the translation works, go to the next step. Perform a translation within Teamcenter. If the translation fails, it is a Teamcenter dispatcher client issue. After the issue is identified as a Teamcenter dispatcher client issue, you can further isolate the problem by setting debug levels to higher values in the log4j2.xml file. More debug information is available in: Console in which the dispatcher client started. Service logs are available in the Log-Directory/Dispatcher/process/DispatcherClient.log file. Task logs are available in the Log-Directory/Dispatcher/Task-ID/Task-ID_ts.log directory. Delete or back up old logs to ensure that you are not looking at wrong files for debug messages. Create a new query for DispatcherRequest using Query Builder. This is useful to check whether the DispatcherRequest object is created in the Teamcenter database. Shut down the dispatcher client. Use the on-demand dispatcher client to trigger a translation request. Start the dispatcher client. Check the console, the DispatcherClient.log file, or task log files to see whether the dispatcher client was successful in extracting files from Teamcenter and uploading them to a staging location. Confirm that files are in a staging directory. If extraction does not occur for the translation request, query DispatcherRequest in the rich client to see whether a DispatcherRequest object is created. After extraction, the task is submitted to the scheduler. Check whether the task was successfully submitted to the scheduler and that you get back a translation successful event from Dispatcher Server. The Dispatcher Server events should appear in the following order: Submitted the task successfully Started translation Completed successfully Confirm that result files (JT, CGM) are available on the file server staging directory. If translation fails, you get a translation error event. If translation fails, use input files in the file server staging directory to translate independent of dispatcher client using Dispatcher Server administration client or the core standalone translator. If translation fails, the input files have some problem. Check whether the dispatcher client was successful in downloading result files and attaching result files back to Teamcenter. If the download is successful and the attachment failed, check whether file mapping failed (file mapping fails if result files do not map one on one with source files). This can occur if translators are not configured per dispatcher client requirements.