| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
Below are the most common problems clients report in tickets concerning the XTM Workbench application.
...
Issue description & Solution
Session has expired when a user is working in XTM Workbench
...
An error like this might be caused by many different factors such as plugins, users user mistakes, user’s long periods of user inactivity (30 minutes of idleness), etc.’ However, there are two most frequent mistakes is one frequent mistake that clients make, that lead leads to the shutting down a of an XTM Workbench session, and those are:
closing out the XTM tab from which the Workbench tab originates;
...
. This is the following:
logging out from the XTM Cloud platform while working in XTM Workbench.
A few minutes after closing the tab/logging user logs out, the session ends. This is a safety mechanism , that prevents any unintended person from editing translation with just with a given particular Workbench session session URL.
Solution: In consideration of the foregoing, please make sure Bearing this in mind, ensure that you are not closing the XTM application tab after opening Workbench in a new one or not logging out form from the XTM Cloud application at all.
If the above is not the case, we suggest that you check if you are using the latest version of your web browser and whether you have disabled any unnecessary plugins or add-ons. If the plugin in your browser affects cookies, it may also have the effect on might also affect the session expiring. The problem in question may This issue can also occur when another user is logging into the same web browser at the time.
Basic steps you can execute take to eliminate identify the potential cause of this issue:
clear your browser's cache (see Clear your web browser's cache (please, click here , cookies, and history for help);
Try another browser;
Try accessing XTM in the private ,
try a different browser,
try accessing XTM Cloud in a private window (“Incognito”) mode;,
Run run your browser without plugins or extensions (please, click here see Disabling plugins for help);,
Check check if your internet connection is stable;,
Check check your proxy or and firewall settings;,
Work work in the single browser mode.
If all above fails these measures fail to improve the situation, please, send the XTM support International Support team all the required information listed below:
Precise Exact date and time range when the issue appeared;occurred,
XTM Workbench instance ID (please, click here see How to obtain XTM Workbench URL (XTM Workbench instance ID) for help);,
Name of the project and of the file you were working on when the issue appeared;,
Name of the user who is experiencing this problem.
| Info |
|---|
In XTM Workbench, you can simultaneously work on more than one file/document at the same time. When the user will log has logged out from the PM GUI (from the current user account), the session opened in a separate tab should expire soon (after approximately after 3-7 minutes). |
After
...
you open XTM Workbench for the affected project, you
...
see the
...
"INITIALIZATION_
...
ERROR" message
...
You will also encounter a problem with target file generation in Project editor → Files. The error will be labeled “Empty document manager“:
...
The above This issue stems from “de-serialization” of files' headers on the "deserialization" of file headers in the XTM Cloud back-end side of XTM.
Solution: There are two solutions to this problem:
Reanalysis of the whole entire project;
Manual repair of the issue by the XTM support International Support team.
In the case If you cannot allow yourselves to perform the re-analysisreanalysis, use the second solution needs to take effect. In this case, please, raise a support ticket and provide details. In it, to save time, send the XTM Workbench ID from the moment the problem kicked in occurred (please, click here for help). The XTM support International Support team will take it from there.
Once we inform you |
|---|
that the problem has been |
|---|
resolved, close the XTM Workbench tab, open the file up once again from the Project Editor → Workflow and check if it opens correctly. You can |
|---|
also generate a target file for the affected file. |
|---|
Grey screen upon entering XTM Workbench
...
Solution: The issue is most likely related to WebSockets. Please, click Click here here for more information and troubleshooting guidelines.
XTM Workbench failed to open
...
because it has already been opened in another tab
...
As the text suggests, the The message:
This document is already open in another window/tab. Continue your work in the opened window/tab or close it and reopen the document.
simply indicates informs you that you must already have a an active XTM Workbench active session of containing this file opened up open elsewhere within in your browser. This is a security measure that prevents anyone from modifying the very same part of a file from different places at the same time.
Solution: Please, make sure Ensure that you have only one XTM Workbench tab opened open at a time by closing the rest. If you still experience the issue, please, execute perform the basic troubleshooting steps specified with in the first issue above.
Segments locked up in XTM Workbench due to no editing rights
...
This issue occurs when you happen to enter Workbench open XTM Workbench in <em>“Read-only</em> mode, for a given file in the “Read-only” modeparticular file.
Solution: Please, make sure Ensure that the Read-only option is unchecked not selected when accessing XTM Workbench.
...
Segments locked
...
in XTM Workbench by another user
...
Our editing tool allows only permits one user to operate on a given particular part of the document at a given particular time. If, for example, you have your file opened in the 1-100 segment range, the second user who attempts to access that part of the file will have them locked up owing to the previous user’s session being in effectfind that they are locked because the previous user's session is still active.
What is more, if another user enters the subsequent next workflow step right after the preceding step is finished, they the segments will also have segments be locked out.
This, as As in the case of the previous issue, this, is yet another security measure, this time preventing . It prevents two linguists from modifying the very same part of a file by two linguists at the same time.
Solution: This behavior can be modified by the utilization of using different workflows, but as a rule of thumb, you should just close out the XTM Workbench window, wait patiently for around 10 minutes and then enter start the editor again.
In some rare cases, if a user closes improperly XTM Cloud incorrectly, with the XTM Workbench opened, his that user's session (still opened open in XTM Workbench) can linger for a while, blocking your access to segments as though the user was still working. In such cases, waiting around 5 minutes before accessing the file again should help.
If the lock is only on one file and does not time out after some durationfixed time interval, moving your workflow back or forth solves the issue.
XTM Workbench cannot be opened for subcontracted projects
...
In the vast majority of cases, the message above message pops up when opening a Linguist opens XTM Workbench for projects which are subcontracted.
Solution: The issue is caused by the fact that there is an ongoing update/upgrade on the contractor server , which blocks all the connections to it. Once the operation is has finished, you should be able to access the XTM Workbench without any issues. Please, stay Stay in touch with your XTM Cloud project managers, to be updated receive updates on the process.
Alternatively, the connection between the servers has collapsed, failed and both the Contractor and you would need to re-establish reestablish it by verifying the connection details in Users → LSPs → (select an LSP) → LSP editor → Connection → Connection information from the LSP.
...
If the two above cases have been checked , yet but you are still are not able to access XTM Workbench for those projects, please, create a proper suitable ticket to for the XTM International Support team and provide all the details.
Specific TM match is inserted automatically into the target segment
When opening XTM Workbench, you might often find your target segments already populated with TM matches, or a TM match is inserted into a specific segment once you go to it.
Solution: As a matter of fact, there are two possible causes for such behavior.
When you open XTM Workbench and see that target segments are pre-populated with such TM match types as ICE Match, Leveraged Match, Fuzzy Match, or Fuzzy Repeat, it means that some of them have been enabled to populate the target automatically, in the global settings of your XTM instance [Configuration → Settings → Translation → TM → (ICE matches | Leveraged matches | Fuzzy matches | Fuzzy repeats) → Populate target with match]. Therefore, consult the settings with your XTM administrators.
...
If you are switching between segments in XTM Workbench in the Edit mode and see that a TM match is inserted as you go, this behavior is caused by XTM Workbench shortcuts, specifically the one mapped to the Enter key. In XTM Workbench, go to Settings → Shortcuts → Matches:
Confirm, go to the next incomplete segment selecting best match,
Confirm, go to next segment selecting best match if segment incomplete.
...
As has been shown in the screenshot above, by pressing enter XTM will complete the segment, go to the next segment and select the best TM match. If you would like to avoid this behavior, it would be best to re-map the enter key to a different shortcut, that has not yet been used in your mapping.
| Info |
|---|
The XTM Workbench shortcuts are set per user. |