SDL Multiterm 2017 not accessable on some machines via .NET API


We are having issues with our application that uses your MultiTerm SDK 2017 on several PCs.
We are using local multiterm desktop installations.

It works fine on some PCs but we get "Exception:External component has thrown an exception." while trying to connect.
A simple test application fails on those machines

Code snippet:
            try
            {
                Sdl.MultiTerm.TMO.Interop.Application oMT = new Sdl.MultiTerm.TMO.Interop.ApplicationClass();
                TermbaseRepository oLocalRep = oMT.LocalRepository;
                oLocalRep.Connect("", "");
                AppendLog("Connection succesfull");
            }
            catch(Exception ex)
            {
                AppendLog("Connection failed - Exception:"+ex.Message);
            }

Can you help us identify what is going wrong?
Do you have detailed logging on the error?

FYI: The multiterm documentation I found on
https://appstore.sdl.com/language/developers/sdk.html
Namely http://producthelp.sdl.com/sdk/MultitermClientApi/2.1/MultiTerm%20Desktop%20SDK.zip?s=220754|20150929122123|0xc14fa61273cb403b6b17b8063f985709b69a88ee?s=null
appears to be outdated.

Some extra info:
I tested with both these versions of Multiterm 2017: 14.1.2441.0     &   14.2.43908.7
Maybe noteworthy: The reference I add in my C# project is
C:\Program Files (x86)\Common Files\SDL\MultiTerm14\Sdl.MultiTerm.TMO.Interop.dll
(FYI I also tried with C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\Sdl.MultiTerm.TMO.Interop.dll but this is the same binary)
but this file only has version 14.0.1529.0
Could that be related?
I also had to set "Embedded interop Types" to false to make the code (based on your sample) work.

Note: I searched for multiterm on https://community.sdl.com/developers-more/developers/language-developers/# but found no hits.
Let me know if I should post the issue there


Kind Regards,
Frederic Vancraeyveldt
for Yamagata Europe

standalonesdlmultiterm2017.zip

Parents
  • Hi Frederic, 

    I am having the same issues with some of my code that I wrote using MultiTerm.TMO.Interop.dll.

    I have found that if I roll back Windows updates to pre-November 2018, I can run my code. As soon as I install Windows Updates as of Nov. 2018, the TMO.dll produces the errors that you are getting as well. 

    I asked Gerhard Kordmann (developer of GlossaryConverter) and he told me that he is getting many reports as well that the Multiterm is not found by GlossaryConverter. His code is getting the same errors. 

    So, to cut it short, from what I can see - one of the Microsoft updates rolled out after Novermber 2018 breaks it.

Reply
  • Hi Frederic, 

    I am having the same issues with some of my code that I wrote using MultiTerm.TMO.Interop.dll.

    I have found that if I roll back Windows updates to pre-November 2018, I can run my code. As soon as I install Windows Updates as of Nov. 2018, the TMO.dll produces the errors that you are getting as well. 

    I asked Gerhard Kordmann (developer of GlossaryConverter) and he told me that he is getting many reports as well that the Multiterm is not found by GlossaryConverter. His code is getting the same errors. 

    So, to cut it short, from what I can see - one of the Microsoft updates rolled out after Novermber 2018 breaks it.

Children