Terms not fully loading after upgrade to 2017

Question

Just upgraded to 2017 and I'm having a strange issue with MultiTerm. It connects alright to Studio but the terms don't seem to load properly. So let's say I have a string like this to translate: 
 Draw a vertical freehand line 
 If I move into the translation field in Studio, it is now regularly happening that I will get (for example) MultiTerm matches for "draw" and "line" but not "vertical" or "freehand" even though the terms are there. If I move out of the cell, for instance with the up arrow, and then back into the cell, then suddenly all matches appear as expected. 
 First I thought this was an issue caused by the new Fragment Matches feature but after disabling it (yes, I re-started Studio), I'm still getting this problem with not all terms loading. 
 The only think I can think of is that it might be related to the Failed to initialize view 'MultiTerm.Studio.EditorView error which I can't seem to shake fully. I've tried re-installing MultiTerm but that doesn't seem to have worked.

Paul · Answer

Hi Michael Bauer , 
 
Try deleting the index files associated with your termbase and open Multiterm again. Also worth reorganising your termbase. See if any of that helps? 
 
Regards 
 
Paul

Paul · Answer

Hi Michael Bauer , 
 
To delete the index files. 
- when you open a termbase by double clicking the *.sdltb this creates a load of other files (I called these index files). Just delete them all. You only need to keep the sdltb and when you double click it again the other files will be recreated. 
 
To reorganise your termbase 
 gateway.sdl.com/.../communityknowledge

Paul · Answer

Michael Bauer 
 Michael Bauer said: I have logged it internally under CRQ-6274" 
 I checked this, thank you for quoting the reference it makes it easier for me, and the issue has not been resolved as the dev team were unable to reproduce this after the 2015 CU10 and 2017 CU5 updates. 
 I have added a note that you are experiencing this in the latest version of Studio/MultiTerm and will let you know when I get some feedback on this. 
 Michael Bauer said: When I try that, I get a garbled page 
 
 from which I'm guessing that this feature is only open to someone with a support contract. 
 That would be correct. This doesn't mean you can't report an installation issue, it just means you don't have access to the support system in the same way as you would if you had a support contract. Create a new case.

Paul · Answer

Michael Bauer 
 The dev team have also reproduced this issue and have scheduled some time to try and resolve this within the next update.

Trados Studio > 3. MultiTerm

Terms not fully loading after upgrade to 2017

Top Replies