Object reference not set to an instance of an object - error message with MultiTerm - Studio 2019 SR2 - 15.2.8.3007

Good morning everybody,

I upgraded my computers from Windows 10 to 11 and purchased new computers at the same time. Before the change, I returned the Studio 2019 licence and have now successfully reactivated it.

While Studio itself works well, MultiTerm is causing a problem: although I have recreated my current project, MultiTerm is not responding and I get this error message when I try to add terms to the selected term bank during translation. Term recognition and database search don't work either.

I am also unable to edit or add terms in MultiTerm itself. I have also saved the term bank under a different name in a different location and tried again, but the error message remains the same.

Any ideas as to what the problem might be and what I can do to reactivate MultiTerm both in Studio 2019 and MultiTerm itself?

Is there any chance to get direct support from RWS without a maintenance agreement in such a case? If so, where could I get it?

Thanks a lot indeed - your help is highly appreciated.

Jutta

emoji
Parents Reply
  • Hi Elisa,

    Thanks a lot for your reply.

    At the moment my 2019 licence is active and working. Studio and also MultiTerm are at the latest version. I planned to finish my current project on 2019, but now it sounds like a good idea to upgrade.

    What would be the workaround to do this upgrade to Trados 2022 Freelance Plus?

    Can I upgrade directly from 2019 to 2022?

    Would I have to download Studio + MultiTerm 2022 first and then click on upgrade? Because when I get there it says it deletes the 2019 licence... would be okay as long as the new version works afterwards. :-)

    Thanks a lot indeed for your support.

    Kind regards,

    Jutta Mansutti

    emoji
Children