Error, the first line of code [Sdl.MultiTerm.TMO.Interop]

Former Member
Former Member

**************************************************************************************************************
[Conclusion]
SDL Trados Studio 2017 SR1 - "14.1.10017"  BUG
**************************************************************************************************************

Hi

I am trying to write some TB codes.
But, at the very first line I have difficulties.

Sdl.MultiTerm.TMO.Interop.Application myApplication = new Sdl.MultiTerm.TMO.Interop.Application();

Error
System.Runtime.InteropServices.SEHException
HResult=0x80004005
Message=외부 구성 요소에서 예외를 Throw했습니다. ( <- it means "external configuration element Throw an exception")
Source=<Cannot evaluate the exception source>
StackTrace:
<Cannot evaluate the exception stack trace>

Any good tips ?
Thanks



tried both;

C:\Program Files (x86)\SDL\SDL MultiTerm\MultiTerm14\ Sdl.MultiTerm.TMO.Interop.dll
C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\ Sdl.MultiTerm.TMO.Interop.dll

I am writing WinForms application.
SDL PlugIns working well, exactly the same code though - and made at the same time, Now...

 

Parents
  • Former Member
    0 Former Member 9 months ago

    I have gone to OLD version.
    With "System mirror" (Backuped image).
    So... There is no error message at all

    All works fine

    That was a BUG

  • Former Member

    Can you send us the exception message; the inner exception should tell us where the excpeption derived from (memory, access violation, version of net etc...).  The message you have is actually quite generic so we can't tell much from that alone.  The full xml error stack would be more useful.
    We have quite a lot of our own 2017 apps and we have not done anything in particular to them to ensure they still work with the latest updates.  The exception being the newtonsoft.dll which we used to provide in several of the apps.  We now point to the Studio version instead as the Studio team increased the version of this dll in the recent updates and this broke half a dozen of our apps... we fixed this already in our plugins.
    And SDL didn't bother to publicly document these changes, as they apparently don't care about the external developers.
    Indeed, the ones above were not documented and came as a surprise to our app developers too.  Sorry you always feel the need to use such unhelpful language given the SDL people in here are always tryng to help.  I'm sure you could make your point more professionally.
  • Indeed, the ones above were not documented and came as a surprise to our app developers too.

    Isn't that extremely weird and alarming? That's a sign of something not quite okay inside...

    I never said that you or other people active in the forum do not help.
    But what's all the good individuals' effort worth when it's all being ruined by what the company does...

  • Former Member
    0 Former Member 9 months ago in reply to Paul

    now, I can not reproduce it any more, as I have gone back
    several seconds earlier I have posted (at comment) full code of mine

    Regards

  • Isn't that extremely weird and alarming? That's a sign of something not quite okay inside...

    Well... welcome to the real world!  Show me a company with as many moving parts as we have that operates perfectly?  We are striving to improve.

    I never said that you or other people active in the forum do not help.

    Of course you did.  We are not separate people... whenever you refer to SDL you refer to us all.  I think we are pretty open about our failings and in this community we do our best to try and help our users when they hit problems, whether they are caused by the users themselves, and when they are caused by us.

    At the same time we also feedback all the problems we find all of the time and the teams behind us do make every effort to improve things.

Reply
  • Isn't that extremely weird and alarming? That's a sign of something not quite okay inside...

    Well... welcome to the real world!  Show me a company with as many moving parts as we have that operates perfectly?  We are striving to improve.

    I never said that you or other people active in the forum do not help.

    Of course you did.  We are not separate people... whenever you refer to SDL you refer to us all.  I think we are pretty open about our failings and in this community we do our best to try and help our users when they hit problems, whether they are caused by the users themselves, and when they are caused by us.

    At the same time we also feedback all the problems we find all of the time and the teams behind us do make every effort to improve things.

Children
No Data