• State Verified Answer
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 433 subscribers
  • Views 7648 views
  • Users 0 members are here
Options
Related

Can't add, can't edit terms in both Studio 2015 and Multiterm 2015 after SR1. "Value cannot be null. Parameter name: input"

Wojciech Matyszkiewicz

Hi,
I'm new to the forum and also new and proud user of Studio 2015.
However, I have one big problem here. Whenever I wish to EDIT or ADD a term in my termbase - either from Studio 2015 level or in Multiterm 2015, I get this message: "Value cannot be null. Parameter name: input" and I can't do anything, but cancel editing.
Interestingly, adding and editing terms works with the older 4809 version, but (at least in my case) not with the newer one... I returned to 4809 and editing terms worked perfectly, then updated again to 4961.2 and... it's not working anymore.
Below is the link to the video to present my problem...
https://youtu.be/70KTb8k6QnA
I'd be so glad for any help.
Once again - adding and editing terms works only with 12.4809 but not with the new version...
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Walter Blaser

    Hi Walter,

    Yes, of course - I upgraded Multiterm as well, and to make matters worse the same problem appears in Multiterm (i.e. "value cannot be null... ").
    I also tried to combine Studio 4961.2 with older Multiterm, but then instead of "value cannot be null" message I simply couldn't even load any termbase.
    I have already tried several things: uninstalled and installed both Studio and Multiterm, uninstalled my Internet Security because someone here had an exactly the same problem as me, but in their case it was solved by uinstallation of AV software. In my case it didn't help at all.

    I thought that perhaps my termbases were corrupt, but I created a fresh termbase and the same problem appeared.
    I also tried removing the SDL folders in Local and Roaming folders to get clean settings, but nothing has helped so far...
    I'm running out of the ideas.
  • 0 in reply to Wojciech Matyszkiewicz

    Hello Wojciech,

    If you have completely uninstalled the previous versions of Studio and MultiTerm, and reinstalled the correct versions and this still occurs then I suggest you log a support ticket so a support engineer can help you resolve this.  

    Go to the Knowledgebase, go to the tab called Solution Finder and now go here;

    Download & Installation Problems
    - I use SDL Trados Studio and/or SDL MultiTerm 2009, 2011, 2014 or 2015
    -- The installation went fine but now I get an error message etc
    --- The problem occurs in (pick the appropriate tool/s)
    ---- None of the articles resolved my problem (if they didn’t!)

    Follow the route for your problem and if there is no answer that helps by the time you get to the end you'll be presented with a form to contact support. Complete all the fields in the form making sure your email address is entered correctly or nobody will be able to get back in touch with you.

    Also use the Chrome browser to log the case if you have it; you'll get more success in completing the form.

    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 Wojciech Matyszkiewicz
    Wojciech

    I watched your video and what surprises me is the caption of the error message window you get "Connecting to web page ..".

    What type is the termbase you have assigned to this project? Is it a server-based termbase? If yes, which version of GroupShare is the hosting server running?

    Does the problem also occur if you assign a file-based termbase? Please try this, just to narrow down what could be causing this.

    Walter
  • 0 in reply to Walter Blaser

    I'm happy to announce that the problem was resolved with the much appreciated help of the support staff. I'm not sure what the reason for the problem was (probably the installation of the studio without "Run as Administrator" command), but now it finally works, so I'm happy again :)

    Walter, as I replied in the proz.com forum, I actually don't know why the caption of the message referred to a web page, as I have only file-based termbases...

    Anyway, thank you all for your efforts!