With respect to "The server threw an exception" Trados says that "This problem is not occuring with Trados 6.x" It occured to me with Trados 6.5 (and I am not the only one as you can see from the links at the bottom). The other message appeared the second time (!) I tried to repeat the same clean up procedure to an rtf file.
My solution? Do not try to find a Trados solution for this. Instead, run Wordfast and click Ctrl+Alt+Q (or click on the "Quick clean up" icon) - problem solved!
Another solutionAnother solution is to clean up directly from Word.
1. Save the original with another name.
2. Press
ALT+F8 for the macro list to appear. Find the macro
tw4winClean.Main and run it.
3. You will need to clean up header/footer, text boxes, manually for all sections in your document with the same macro
SYMPTOMS
When running a batch analysis, translation or clean up on Microsoft Word documents that contain circular RTF style references, the following error message may appear in the status bar of the relevant dialog box and in the log file: (-2147417851): RPC_E_SERVERFAULT (The server threw an exception.) File skipped! When running a batch translation or clean up, only the backup file (*.bak) is created. The target file, however, appears to be missing.
Error Number: -2147417851
Error String: RPC_E_SERVERFAULT (The server threw an exception.) File skipped!
EXPLANATION
TRADOS confirms this to be a problem in one of the components of Translator's Workbench 5.5 (Build 247) and has made a patch available to correct this error in the relevant component (TRADOS5TM.dll). After applying the patch, Translator's Workbench will no longer skip *.doc files that contain circular style references.
STEPS
This patch has been superseded by the more comprehensive and more recent cumulative patch from October 2002 that you can download from article no. 1127 (Trados 5.5 Corporate Translation Solution and Service Provider Suite) or article no. 1128 (Trados 5.5 Freelance). We recommend that you download the patches available from these articles.
ADDITIONAL INFORMATION
This problem is not occuring with Trados 6.x (all versions)
Links
http://www.proz.com/topic/16271http://www.proz.com/topic/29344http://support.trados.com/view.asp?cntID=1090