After installing a Java 7 runtime environment last week, I experienced a problem with SDL Multiterm 2011. If you happen to have a non-functional Multiterm after performing Java update, you may try whether the following solution works for you.
Here are the symptoms:
After Java 7 update, it is impossible to add new records into Multiterm termbase. The application itself opens correctly, but when you try to add a new unit, nothing is shown on the term tab. The application itself does not crash, it just does not run correctly.
This situation happens both when trying to add a new term in Multitem and in SDL Trados Studio.
The problem may be caused by the “Next-generation Java Plug-in” setting in the Java Control Panel. What we need to do is to update this setting in Java Control Panel.
Multiterm uses Java 6 runtime environment (26). If your computer has Java 7 runtime installed, you may face the same problem I had that the Control Panels contain an icon for Java 7 only.
Open Java Control Panel for version 6_0.26. Run the Windows Explorer, browse to Program Files, locate Java > jre1.6.0_26 > bin and double-click the javacpl.exe file. Required version of the Java Control Panel is launched.
Click Advanced tab, click “+” next to the Java Plug-in and uncheck the “Enable the next-generation Java Plug-in (required browsed restart)” checkbox. Click OK to exist the Control Panel.
Test whether this fixed the Multiterm problem. If the problem persists, try to restart the computer. If the situation remains the same then this solution does not work for you and the problem has another cause.
Uninstalled all other versions of Java just to make sure.
Now works perfectly.
Bit of a pain. I hope SDL can keep up with their Add-ins
Thank you for your fix for this annoying problem. I applied it to Java 6 Update 29 (build 1.6.0_29-b11) and it worked after restarting my computer. Thanks again!
Thanks Michal, it looks like this solved my problem, too.
What a lifesaver! Thanks a lot for this!
No need to install other versions of Java for me, works great.
Excellent fix!!! Thanks a million!
Thanks a lot. I tried many solutions found on the internet and nothing worked but this solution does!
You are a genius!!! Many thanks!
I have been struggling with this for a while and now perfect!!!
You are welcome!
You’re my hero, a thousand times thank you!
Another update, another Multiterm failure, but thank you for this fix; it was relatively painless this time!
Happy New Year to you.
Thank you for this fix! I’m working on a major high-terminology project atm, and being unable to add new entries to my MultiTerm database was really annoying. Your fix worked perfectly, and I can finally get to work properly!
It half fixed my problem. Adding making the change mentioned in the article, I could then add terms in Multiterm. But it would not allow me to open the termbase in SDL Studio anymore. It says the termbase was created with an incompatible version of Multiterm.
So before I could use the termbase, but not add terms. Now I can add terms, but not use the termbase!
The only solution I have found thus far is to completely remove Java 7.
My Multiterm works fine with Java 7. On the other hand, behavior of Java-based SDL products is a kind of unpredictable, so I would not be surprised if your MT did not work with Java 7. Good luck with this!
Thank you very much for your hint, it helped a lot!
I have this problem: 2 PCs, each with Trados 2011. Both received same package from the client. When a specific segment is opened on both PCs, different terminology from Multiterm displays. I.e. Multiterm seems to be working correctly, but it does not.
Do you have an idea/solution/workabout? Thanks for any help. Petr
Sorry for late response, I am currently in Japan…
Have you set fuzzy search in Multiterm on both PCs?
Indeed that helped. My system autoupdated to Java 8 (u31), and multiterm stoped working. Previusly had my settings on java 7 setted to minimum and i had to confirm java apllet to run manually – made me nuts! Uninstalled all versions of Java, installed Java 6 (u29), turned off autoupdates and voila, it works like a charm.