• State Suggested Answer
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 436 subscribers
  • Views 7546 views
  • Users 0 members are here
Options
Related

Term recognition stops working in trados 2017

Bruno Depascale

Hi everybody, I hope somebody can help me with this issue. 

In the middle of a project, Trados 2017 suddenly stops recognizing terms and the term recognition window looks empty (even if the termbase contains many of the terms in the source text).

If I shut down trados then the problem disappears and it works fine for another half an hour.

As you can see from the attached screenshot, the term "emphysema" is in the dictionary but trados doesn't recognize it.

(by the way, I am using the latest version of multiterm and trados)

Can you help  me?
Thank you! 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi Bruno,

    If this works to begin with I wonder if you are hosting your termbase on an external drive or dropbox for example? Can you try and reorganise your termbase and see if this helps?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Dear Paul,
    thank you for your answer. Indeed, I host the termbase and TMs on dropbox. Is that a problem? I'll try to reorganize the termbase and I'll let you know if this solves the problem.
  • 0 in reply to Bruno Depascale
    Hi Bruno,

    It could be... probably depends on the type of consistently good connection you have. Can you also try moving your termbases to a local folder on your computer and work with it for a while. See if that's better for you?

    Regards

    Paul

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

    Dear Paul,
    I have moved my termbases to a local folder (no dropbox). The problem in object indeed disappeared but other problems emerged. for example, trados started to crash several times unexpectedly (10 times per day). So, following your suggestions in other threads, I removed trados and reinstalled it. It stopped crashing but yet another problem emerged: I cannot add terms within trados studio to the termbase due to the following error message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (you can find the details below).
    I tried to reorganize the termbase, but the problem is still there. What am I supposed to do?
    Thank you for your help
    Bruno

    -------------------------

    <SDLErrorDetails time="11/10/2017 10:58:45">
    <ErrorMessage>Attempted to read or write protected memory. This is often an indication that other memory is corrupt.</ErrorMessage>
    <Exception>
    <Type>System.AccessViolationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.MultiTerm.TMO.Interop</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[ at Sdl.MultiTerm.TMO.Interop.TermbaseDefinitionClass.get__Schema()
    at Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.GetSchema()
    at Sdl.MultiTerm.Client.UI.Viewer.ScriptingHost.set_Termbase(TermbaseStatus value)
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.InvokeShowConceptScript()
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.InvokePageScripts()
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.ShowActiveEntry()
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.Refresh()
    at Sdl.MultiTerm.Client.MiniEditor.MiniEditorControl.Refresh()
    at Sdl.MultiTerm.Client.MiniEditor.MiniEditorControl.TermViewer_TermSaved(ITermHit term)
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.TriggerConceptSaved()
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.SaveNewConcept()
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.SetupNewConcept(String source, String target)
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.AddNewConceptWithTerms(String source, String target)
    at Sdl.MultiTerm.Client.UI.Viewer.DefaultTermViewer.EditNewIncomplete(String source, String target)
    at Sdl.MultiTerm.Client.MiniEditor.MiniEditorControl.AddTerm(TermbaseStatus activeTermbase, String source, String target)
    at Sdl.MultiTerm.Client.MiniEditor.MiniEditor.AddTerm(TermbaseStatus activeTermbase, String source, String target)
    at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(ITermbaseInfo termbaseInfo, String source, String target)
    at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.MultiTermViewerWinFormsUI.AddTerm(String source, String target)
    at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.TerminologyProviderViewerAddTerm(String source, String target)
    at Sdl.TranslationStudio.Editor.Terminology.TermbaseViewer.TermBaseViewPartX.AddTerm(ITerminologyProvider termbase, String source, String target)
    at Sdl.TranslationStudio.Editor.Terminology.EditorTermbaseUtils.AddTerm(IEditorService editorService, ITranslatableDocument translatableDocument, String sourceText, String targetText)
    at Sdl.TranslationStudio.Editor.Terminology.Actions.AbstractAddNewTermAction.AddTerm()
    at Sdl.TranslationStudio.Editor.Terminology.Actions.AddNewTerm.Execute()
    at Sdl.Desktop.Platform.Implementation.CommandBars.StaticAction.Execute()
    at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass3.<ExecuteAction>b__2()
    at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
    at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
    at Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteActionForShortcut(Keys shortcut)
    at Sdl.Desktop.Platform.WinForms.StudioWindowForm.OnKeyDown(KeyEventArgs e)
    at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
    at System.Windows.Forms.Form.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyPreview(Message& m)
    at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
    at System.Windows.Forms.Control.WmKeyChar(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
    </Exception>
    <Environment>
    <ProductName>SDL Trados Studio</ProductName>
    <ProductVersion>14.0.0.0</ProductVersion>
    <EntryAssemblyFileVersion>14.1.6329.7</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1040</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>DESKTOP-Q95VB79\Bruno</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>DESKTOP-Q95VB79</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>3526180 MB</PhysicalMemory>
    </Environment>
    </SDLErrorDetails>
  • 0
    Hi, I had this problem too.

    My project folder with 2 termbases gets syncronized with Google Drive and this could be a problem.

    I add words continously in the primary termbase when translating, but this termbase stops to show words in the Term Recognition window. If I use the Termbase Search to find the words. Trados finds the words in the termbase. The second termbase keeps to show words in the Term Recognition window.

    I tried to reorganise the primary termbase, but Multiterm crashes before finishing the reorganisation. I have tried several times. Then I put the primary termbase in a folder on the desktop and then the reorganisation was successful.

    I copied back the primary termbase in the project folder in the folder which gets syncronized with Google Drive. Now the Term Recognition functions again. And until now it still works even if I have added more terms to the primary termbase.

    So the problem can´t be the fact that I use syncronization with Google Drive, but I don´t think it was a coincidence that Multiterm was crashing all the time, when I tried to reorganise the termbase when it was in the folder which gets syncronized with Google Drive.

    Best regards
    Thomas
  • 0 in reply to Thomas Langer
    Hi again, more feedback in this matter: After working a while a recently added word again did not appear in the Term Recognition window. Other words from the termbase are shown. I once again did a reorganisation - this time I could do the reorganisation in the folder which gets syncronized with Google Drive - and now the word is shown in the Term Recognition window. I don´t know what the problem is, but to reorganize the termbase so frequently is not really a solution.
  • 0 in reply to Thomas Langer
    I'm having the same problem and my termbase is in a local folder. Judging from a few other threads on similar issues, this seems to be a known problem that SDL is working on, is that right? Any news?
  • 0 in reply to Charlotte Sjögren

    This problem has existed for years and years and years, and there does not seem to be any way to fix it, apart from if SDL decide to change the underlying database format (Access/Jet). I have NEVER gotten Studio (2014, 2015, 2019) to reliably recognise terms I know are in my termbase, no matter how small or new or correct the termbase, no matter whether I reinstall Studio from scratch, reorganise the termbase, Repair the installation ,etc. None of this works because the problem is systemic. That is, the terminology recognition system just does not really work very well in Studio.

    They recently moved the TM database system to SQLite (which was a great idea), so all we can do is pray they decide to finally ditch the crap underlying database engine termbases / term recognition relies on. Until then, no matter what you do, you will never really know if a term is already in your termbase.

    Michael
  • 0 in reply to Michael Beijer
    Hmm, by the way, out of frustration, I have been testing all of the different terminology systems offered in Studio 2019, so I tried SDL Language Cloud (Beta) next. And guess what: exact same problem. More than half of what I enter in my termbase, or is already in it, is not recognised. Very sad.

    By the way, term recognition works flawlessly in CafeTran, memoQ, Déjà Vu, and many other CAT tools, so it isn't rocket science.
  • 0 in reply to Michael Beijer

    Also just tested "Excel based terminology provider" (available via TermExcelerator): same problem: zero recognition.

    The only way I can force the Term recognition to recognise newly added terms is to:

    1. add another term, and

    2. save it, and then

    3. click back and forth (up/down) through the segments a bit, and

    4. … eventually … all new terms will be recognised.

    (btw, I just tried the above steps, over and over, and it is 100% reproducible. Paul, you reading this?)

     

    This leads me to believe the faulty term recognition problem is not due to the underlying database format (as I suspected), but due to the Recognition window and/or the Translation editor.