Troubleshooting common issues
A list of common solutions to potential issues, organized into troubleshooting areas. While this information might not be exhaustive, you can refer to it when trying to understand why WorldServer works in a certain way.
- Java support in WorldServer
Certain WorldServer operations might fail if the supported Java version is not the first Java reference in your path. - Troubleshooting using deployment
Deployment is a way of exporting and importing specific WorldServer objects or configurations. It is particularly useful if something works on one system, but not on another, because you can use these objects to identify where and why the issue is occurring. You can export and import objects either through the user interface or through a command-line tool. - Issues occurring throughout the translation process
Common issues that occur throughout the translation process include projects not being created or the translation memory showing little to no leverage. Here are some common symptoms and causes of such issues, as well as solutions that will help you avoid them in the future. - Troubleshooting encoding issues
A series of steps that you need to check if you still encounter encoding-related issues after upgrading to the latest version of WorldServer. - Troubleshooting issues related to language codes and custom cultures
WorldServer supports a very large number of custom cultures. In certain situations, this might lead to language code inconsistencies or to compatibility issues with other translation tools, such as Trados Studio. This section aims to help you prevent such issues or to provide quicker resolutions. - Troubleshooting object imports and exports
A list of tasks that you need to perform when troubleshooting issues related to import or export actions. - Troubleshooting configuration issues
Starting with WorldServer 11.1, a series of /wsgate endpoints have been created, which you can use to see the configuration values and the localization messages loaded at runtime. You can use them to pinpoint configuration issues which might otherwise be time-consuming and difficult to find. Only administrators can access these endpoints and no passwords are exposed when accessing them. - Troubleshooting Firefox issues
If you do not have a file compression tool installed on your system, the .zip extension might not be associated with the correct MIME type in Firefox. For example, if you upload a .zip asset when creating a project in Firefox, WorldServer might treat the asset as a single file, rather than extracting all the files in it, as expected. There are two possible workarounds for this issue.