Troubleshooting Desktop Workbench
When working in Desktop Workbench, use the following information to help troubleshoot suspected issues.
Note: Desktop Workbench cannot be used for any assets processed by Studio file types and handled by the File Type Support (FTS) server.
Troubleshooting Area
Suggestion or Relevant Information
Alternate Client
Try running Desktop Workbench with the same set of files on another client. If the issues persist, you have a basis with which to compare behaviors.
Options Dialog Box
The Options dialog box ( Tools > Options ) contains numerous settings, the values of which could be influencing a behavior in an unexpected way. Check settings in the Options dialog box first, before assuming you have encountered a more serious issue. For example, the font setting for a particular language can affect how specific characters display. Be sure that the font associated with a language allows for display of the characters in the language. Also, database lookup values may be set too high if some translation memory matches are not available when they should be.
Importing
If, when importing a translation kit into Desktop Workbench, you see the Upload Completed dialog box but still see errors within the screen, approach the issue as an XLZ import issue. See the information on importing and exporting projects in this Troubleshooting section.
Logging In
If, when logging in to Desktop Workbench, the user receives the message, User has no permission to run Web services, then the user type associated with the user does not have Web Services enabled. Web services must be enabled for the user’s type for the user to log in. If the user is unable to connect to a remote server, first make sure that the WorldServer URL is specified–and spelled–correctly. If the URL is populated automatically, be sure that the url_of_origin setting in general.properties is correct. Once login is successful, the upload happens automatically. If the upload fails, try uploading the Desktop Workbench-exported translation kit manually from the Project Page in WorldServer.
Scoping Differences
Scoping in Desktop Workbench is different from scoping in WorldServer. For consistent scoping, use the Download Scoping Configuration option.
Saving Changes
Desktop Workbench saves all changes as they are made, so you do not need to save changes manually. This also means that you cannot undo changes unless they are in manually typed translations.
Placeholder Matching
Placeholders in a target asset must match the placeholders in a source asset. To check an asset for placeholder errors, use Translation > Check Placeholders . To resolve placeholder errors, perform one or more of the following, as appropriate:
  • Add missing placeholders manually ( {<id>}, for example, {45}).
  • Add or correct missing placeholders by coping and pasting them from the source asset.
  • Delete extra placeholders.
File Locations
Files commonly used or needed by Desktop Workbench are located as follows:
  • C:\Program Files\Idiom\Translation Workbench\Workbench.log
  • C:\Documents and Setting\[PROFILE]\My Documents\Idiom\My Projects
  • C:\Documents and Setting\[PROFILE]\My Documents\Idiom\My TDs
  • C:\Documents and Setting\[PROFILE]\My Documents\Idiom\My TMs
Submitting Desktop Workbench Issues
If you encounter the dialog box with the automatic error reporting facility, please use it. Regardless, include the following information when reporting Desktop Workbench issues:
  • original untranslated kit
  • translated kit
  • workbench log file
  • steps to reproduce
Parent Topic
Troubleshooting