email:   password:  

The Wordfast Knowledge Base
To contribute an article, log in from community > registered users
Knowledgebase Home Page > @ Wordfast Professional > WFP Troubleshooting
Search the Knowledge Base Browse by Category
Title: Common Errors
Author: Yasmin Moslem
Quick link to this article:
Article last updated: 2010-08-18 05:04:08
Print this page
Email it to a friend
Contact the author


Importing a tab-delimited glossary, special characters or non-Unicode language characters are not displayed properly.

Convert the txt file of the tab-delimited glossary to Unicode before importing it into Wordfast Pro. To do so, open it in NotePad (Windows) or TextEdit (Mac) and select “Save as”; under “Encoding”, select “Unicode” or “UTF-8”.


“Failed to connect. Problem getting encoding for tm.txt”

If you receive this error while trying to open a txt TM, convert your TM txt file to Unicode. You can use NotePad: File > Save as > Encoding > Unicode, or you can use Wordfast Classic Data Editor > Tools > Special Filters > Rewrite TM as Unicode.


"Failed to make a search.... Error in concordance search"

This error happens when you forget to type one of the two quotes in the TM Lookup text box. So, make sure that your phrase is actually included between the quote pair.


"Failed to connect. Translation memory header is invalid"

Receiving this error while trying to open a txt TM may be due to one of the following reasons: 1) language code is incorrect (open in NotePad and find-replace), 2) Trados txt TM (convert to TMX), or 3) missing % (open in WFC - Reorganize).


TM Connection Error: “Failed to leverage segment. Unknown Wordfast escape {letter} in source.”

Solution 1: Open the TM in a text editor. Search for the problematic letter in the TM and delete it. Solution 2: Open the TM in Olifant; it will exclude any problematic TUs including errors. Save the TM file with a new name.


"Skipping empty target language at line ...".

Receiving this error while trying to import a glossary may be due to: 1) the target equivalent is missing for this source term, or 2) there are more than *one tab* between each term and its equivalent. Removing the extra tabs enabled Wordfast Pro to import the glossary successfully.


“Checksum failed. Original file could not be found it’s either renamed or changed. Would you like to locate it by yourself?” or “Checksum error” for filepath.txml during cleaning up.

Click on “Yes” for "Would you like to locate it yourself?” Then just choose the source file. For successful “Cleanup”, make sure the original source file is in the same folder as the TXML file.


“wf://EN> Failed to connect. could not connect to TM server as EN>FR (Permission denied: connect).”

Receiving a similar error while trying to create a new Remote TM may be due to security software. Try to disable any security software or adjust Firewall settings to see if this makes difference.


“Tracking changes detected in document. Please accept all tracking changing before loading.”

1) Please open the original doc file in MS Word and disable "Track Changes", save. 2) Open the original doc file (after disabling "Track Changes") in WF Pro.


“An internal error occurred during: “Update Manager”. SHA1 digest error for about.html

To use Wordfast Pro automatic updates on Windows Vista, you should first turn off the UAC; you can turn it on after updating: (Control Panel -> User Accounts -> Turn User Account Control on or off -> (un-check) Use User Account Control) -> Re-start your computer.



“Save Translated File” creates a 0KB INX file.

1)      When you create a .txml file from an .inx file, you should also have a generated .skl file. This is needed and should be in the same folder to be able to save the translated .inx file.

2)      Missing placeables in target cells

3)      Shrinking segments including placeables


“The import terminology file is empty”

This error is usually related to initial asterisks in glossaries imported, i.e. asterisks within the first three letters of any word of the term, which is not supported yet. Any other asterisks (in the middle or at the end or a term) should be OK and functional. Once you remove the initial asterisks, you will manage to import the whole glossary successfully.



WFP crashes while trying to open an HTML file.

This could happen if the HTML file is saved as Unicode while it should be saved in UTF-8 or ANSI. Here is the solution: Right-click each HTML file and select "Open with" > "NotePad". Select "File" menu > "Save as". From the drop-down menu "Encoding", select "UTF-8". Save!

Errors (Remote TM)

Failed to connect. Invalid TM languages.

Open the TM in any text editor (e.g. NotePad) and correct the language codes in the TM header. Note: Wordfast Server does not accept neutral language codes for in the TM header, so you need to change EN to EN-US or EN-GB, for example.

Related Articles:


No attachments were found.

The Wordfast Knowledge Base Copyright © 2015
Contents copyright Yves Champollion

(c) 2015, Yves Champollion
Yves Champollion translation localization consultant consulting. en fran�ais