You are currently working on UAT
Trying to connect to MultiTerm Server using the example code from SDK. This works fine with MultiTerm 2014 but when I install 2017 then it fails
Set oLocalRep = oMt.LocalRepository
I updated the Reference to MultiTerm140.TMO 14.0 Type Library.
Trying in C# code it is also fails (this also works with 2014, and I also updated the References accordingly)
MultiTermApp = new MultiTermIX.Application();
I tried to reinstall MultiTerm, still no luck.
Any idea how to fix this?
Regards,
Judit
Judit Gal (JuditGal)
Hi Judit! Is this the error you get?
Hello, sorry to jump in here, but this is the exact error that I have been getting.
I built a plugin, adding a reference to the "Sdl.MultiTerm.TMO.Interop.dll" in my Trados Studio 2017 folder:
Then, when I install the plugin and start Trados Studio 2017, it seems to say that the version I referenced (which came from my Studio 2017 folder) is somehow different or newer than the version that Trados 2017 is using (which should be the exact same one, which is in the Studio 2017 folder).
By the way, my version of Studio is Studio 2017 SR1 14.1.10016.54660.
Basically, I'm saying that I seem to have one file named Sdl.MultiTerm.TMO.Interop.dll on my computer. Trados Studio seems to use that file. My plugin also attempts to use that file. So, why is Trados Studio giving me an error that the file referenced in the plugin is newer? It is the same file.
Thank you in advance for your answer, I've been trying to solve this problem for weeks.
-- Michael
Hi Michael, our problem with the error was only solved when we installed the recent update (30 May 2019). I guess as the patch note says "Fixed System.Runtime.InteropServices.SEHException error when trying to access MultiTerm API" SDL found and fixed the cause of the problem.
Sorry I can't give you more help but we never managed to identify the exact cause.
I hope the update will help you too.
Good luck,
Judit
Hi Michael, our problem with the error was only solved when we installed the recent update (30 May 2019). I guess as the patch note says "Fixed System.Runtime.InteropServices.SEHException error when trying to access MultiTerm API" SDL found and fixed the cause of the problem.
Sorry I can't give you more help but we never managed to identify the exact cause.
I hope the update will help you too.
Good luck,
Judit
Translate
