• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1758 views
  • Users 0 members are here
Options
Related

Corrupted MultiTerm (2015) Entry after Modification in Trados Studio 2017 (System.NullReferenceException ...)

Matthias Lindner

A few days ago I upgraded from Trados Studio 2015 Freelance Plus to Trados Studio 2017 Freelance Plus. Now, when I modify an existing MultiTerm termbase entry, e.g. add another term, this somehow corrupts the termbase entry. The entry is just not displayed any more in the Studio 2017 term view.

I already reorganized the termbase in MultiTerm 2015 Desktop (SR 2), but this doesn't solve the problem.

Neither is it possible to modify the entry directly in MultiTerm 2015. When I try to save the changes, I get an "Unknown error" with detailed information pointing to a "System.NullReferenceException ...", see attached screenshot.

Replies that help me to solve the issue will be highly appreciated.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Jesse Good

    Hi Jesse,
    thanks for your reply and suggestion. I had not updated to MultiTerm 2017 when upgrading to Studio 2017 because both relase notes and online help of Studio 2017 state that Studio 2017 is fully compatible with MultiTerm 2014, 2015 and 2017 termbases.

    I have installed MultiTerm 2017 SR1 now, and I uninstalled and reinstalled Studio 2017. I have also reorganized the termbase in the new MultiTerm version.
    However, this did not solve my problem.

    Any modification (e.g. merging) of a termbase entry in the termbase view of Studio 2017 will still render the entry unusable or "invisible".

    Any other hints or suggestions?

    By the way: How can I "upgrade" this forum conversation to an actual trouble ticket with SDL?
  • 0 in reply to Matthias Lindner
    Hi Matthias

    Hmm, my only other suggestion would be to switch the default layout to something else. The error seems to be occurring when you are using the new layout (it should be easy to switch right in the multiterm view)

    >By the way: How can I "upgrade" this forum conversation to an actual trouble ticket with SDL?
    Sorry, I don't work for SDL, I will link as he might know the answer to that.
  • 0 in reply to Matthias Lindner

    Unknown said:
    By the way: How can I "upgrade" this forum conversation to an actual trouble ticket with SDL?

    Hi  

    If you have a support contract then you don't log it in here at all, you do it through the Gateway in your MySDL Account.  If you don't have a support contract then you can log a case for installation issues, which this probably doesn't qualify for, using this link:

    gateway.sdl.com/liveagentlicensing

    You have two options:

    1. Submit a case using a webform
    2. Use live chat to get a licence reset

    You would use the first option if your case qualified.

    So we can try and figure out the problem in here.  The first thing is to make sure you have the latest versions of both Studio and Multiterm.  Your comment on the compatibility is irrelevant here because we are not talking about where the termbase came from.  The current versions are:

    SDL Trados Studio 2017 SR1 - 14.1.6413.8
    SDL MultiTerm 2017 SR1 - 14.1.2471.5

    If you have these both installed and still have this problem can you advise whether you can edit the term in MultiTerm itself rather than through Studio?

    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