Adding terms to Multiterm from within Studio 2019 no longer works

After adding some addons to Studio 2019, I can no longer add terms to MultiTerm from within Studio. I get the error message: "Unhandled exception. Error info saved to errorLog.txt file. Error message: 'Sdl.MultiTerm.Client.CppBridge.dll or one of its dependencies. The specified module could not be found.'"

How can this be rectified? 

6 Replies Latest Replies: 26 Jan 2019 9:11 PM by Paul < 1   2  >


  • I'm going to guess that you installed BaccS based on the errorLog.txt file you mention. BaccS captures any exceptions and saves them to that file, even if they have nothing to do with BaccS at all. You might get some idea if you look in the errorLog.txt file which by default you'll find here:

    c:\[USERNAME]\pfilkin\Documents\BaccS\TradosDatabase\

    You could post the txt file here if you like so we can see it?

    However, back to MultiTerm. If the errorlog doesn't show anything obvious then try a Studio reset. You could use this app for the reset and this will also explain what you will lose by carrying out a reset before you do it:

    appstore.sdl.com/.../

    But if you'd rather do this manually then rename this folder (just add _old to the end or something, it's not important what you rename it to) and restart Studio:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0

    So the path would become this:

    c:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\15.0.0.0_old

    If you can't find this folder then you need to unhide your hidden files/folders:

    www.howtogeek.com/.../
  • In reply to Paul:

    Hi Paul. Thank you. Indeed I have recently installed BaccS. Would this problem go away if I uninstalled BaccS? But how would I do that? Just by disabling the plugin? I'm hesitant to do this, because I had disabled a plugin before, after which I could not even start Studio anymore. Fortunately I had a support contract at that time, which solved the issue by remote access.
  • In reply to Friedrich Reinold:

    Indeed the BaccS log is filled with those error message since I installed it!

    New exception entry: 26-Jan-19 13:32:40

    Could not load file or assembly 'Sdl.MultiTerm.Client.CppBridge.dll' or one of its dependencies. The specified module could not be found.

      at Sdl.MultiTerm.Client.UI.Viewer.TermViewer.EditNew(String source, String target)

      at Sdl.MultiTerm.Client.UI.Viewer.TermViewer.EditNewIncomplete(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__DisplayClass30_0.<ExecuteAction>b__0()

      at Sdl.Desktop.Logger.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)

  • In reply to Friedrich Reinold:

     

    Friedrich Reinold
    Would this problem go away if I uninstalled BaccS?

    No.  This problem has nothing to do with BaccS.

    The only reason I mentioned this is because BaccS has a mechanism for reporting exceptions if you have any problems with it.  However, it captures every exception whether it's caused by BaccS or not.

    I think you should do what I also suggested.  Carry out a reset.

    You do not need to uninstall any plugins.

  • In reply to Paul:

    In the meantime I got help from SDL Support to uninstall the BaccS plugin. That was a week ago, and since then I have not had this problem even once with any project. Adding terms to MultiTerm from within Studio 2019 works again as fine as before.
< 1   2  >
Related