• State Suggested Answer
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 190 subscribers
  • Views 3797 views
  • Users 0 members are here
Options
Related

Best practice when working with MultiTerm termbase in Studio?

Michael Beijer

I was wondering what is best practice when working with a MultiTerm termbase in Studio? I sometimes find it useful to keep MultiTerm open, with the term base I am currently using in Studio open. However, I have been having all kinds of problems with my termbases, where they sometimes become unresponsive in Studio, to the point where I have to disconnect/reconnect them from my project to get them working again. I sometimes even have to kill Studio, because it becomes unresponsive when trying to edit a TB entry insight Studio. Another problem I have been having is that the SDL Widget basically crashes all the time (I logged a support case). 

By the way, after my last support session (about the "traverse.js" bug), I was advised to reinstall Windows 10 from scratch. Luckily, I had been planning on doing this anyway. Anyway, I did so, so the problems I am currently having as described above are on a brand-new win10 install, fully updated. 

Michael
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Michael,

    I'm hoping others will chime in here as we do have many users who make a lot of use of MultiTerm. Generally I think most users will only run MultiTerm in Studio so they won't have MultiTerm open in parallel, or run the widget all at the same time... although having said that there is still no reason why this should not work fine. I think as long as they are all the same versions (or versions that were released to be able to run together) everything should work correctly.

    On your errors, I guess you have been through this already as I know you were getting this previously?

    gateway.sdl.com/.../communityknowledge

    Interestingly after you mentioned this I started to get this too when I installed the first Studio 2017 Beta... but this was a Beta issue in conjunction with the first, early, build. The second build resolved this, and I reinstalled Studio and MultiTerm anyway when it first occurred and this cured it there too.

    I'll follow up with support on this as I'm interested to know why you are having problems.

    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

    Yes, I tried all that (https://gateway.sdl.com/apex/communityknowledge?articleName=Blank-page-script-error-or-error-no-such-method-getEntry-when-editing-or-adding-a-term-to-an-existing-termbase), and none of it worked. The SDL support person tried all kinds of stuff, and in the end said it was due to Windows issues, and recommended I fix those, but since I had no idea what they might be, I decided to do a fresh install of win10. It was time anyway, because the copy of Windows 10 I was running was actually an upgrade on top of win7, which itself was getting a bit old and had various problems.

    Anyway, so on this fresh copy of win10, the travese.js error no longer occurs, which is great, but MultiTerm isn't entirely happy, yet. In fact, Studio just froze right now again (as I was trying to do something TB related) and so I am going to have to force quite it again.

    A related question: is it better or worse to run Studio "as administrator"? That is, should I start it from the Start menu normally, or right-click and select "Run As Administrator"?

    Thanks for following up on this!
  • 0 in reply to Michael Beijer

    Unknown said:
    A related question: is it better or worse to run Studio "as administrator"? That is, should I start it from the Start menu normally, or right-click and select "Run As Administrator"?

    Good question.  I install the programs as admin but don't run them as admin and I don't have these problems.  But to be fair, I'm not a translator and I don't spend as much time running these applications all day as you guys do.  So I think my situation is not really apples for apples.

    There do seem to be a couple of common culprits that can cause problems, outside of permissions, and these are anti-virus and automated clean up utilities.  Perhaps, if you can reproduce these issues fairly easily it would be worth switching them off for a while and seeing whether this improves the problems.  At least it would provide a pointer into where else to look.

    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

Reply
  • 0 in reply to Michael Beijer

    Unknown said:
    A related question: is it better or worse to run Studio "as administrator"? That is, should I start it from the Start menu normally, or right-click and select "Run As Administrator"?

    Good question.  I install the programs as admin but don't run them as admin and I don't have these problems.  But to be fair, I'm not a translator and I don't spend as much time running these applications all day as you guys do.  So I think my situation is not really apples for apples.

    There do seem to be a couple of common culprits that can cause problems, outside of permissions, and these are anti-virus and automated clean up utilities.  Perhaps, if you can reproduce these issues fairly easily it would be worth switching them off for a while and seeing whether this improves the problems.  At least it would provide a pointer into where else to look.

    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

Children
  • 0 in reply to Paul

    Hmm, I did a few things, and don't seem to have had the problem since!

    1. I switched off CCleaner permanent monitoring.

    2. I added C:\Program Files (x86)\SDL OpenExchange + C:\Program Files (x86)\SDL to my exclusions list in Kaspersky

    3. I added the folder where I am storing the termbases to my exclusions list in Kaspersky

    But perhaps most importantly of all, I realised that after clicking Quick Add New Term, you still need to save the entry in the Termbase Viewer. I think I was forgetting to do this occasionally, and then quickly switching to somewhere else, which might've caused the problems I was experiencing. In any event, so far everything has gone without any problems.
  • 0 in reply to Michael Beijer

    Unknown said:
    I realised that after clicking Quick Add New Term, you still need to save the entry in the Termbase Viewer.

    Hi Michael,

    This is not correct. There are two add new terms.  The Quick Add New Term and just Add New Term.  You only need to save the term separately if you use the original Add New term.  The Quick Add New Term doesn't ask at all, it adds the term and saves it in one go.

    Really glad you managed to figure where the rest of the problems were coming from though.  I think CCleaner may be a red herring though and reckon Kaspersky is a more likely culprit... at least based on me also using CCleaner in the same way.

    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

    Sorry, what I meant to write is:

    That after clicking Quick Add New Term, you still need to save the entry in the Termbase Viewer ... if the selected term already exists. In this case, if you click "Yes" at:

    ... you do still need to save the entry in the Termbase Viewer.

    Sorry, I'm tired, it's Sunday evening, and I'm struggling to get this large patent application done (so that my wife and I can go to the End Of The Road festival next week!).

    Michael