Update: An upgrade to 2019 does not fix this issue and I'm still having to move the cursor in and out of the target field to "wake up" the term suggestions regularly. Not impressed that such a basic feature can be this buggy.

Hi Michael Bauer

Are you sure that you have updated MultiTerm AND Studio to the most recent version? You can check by clicking on the Help tab in each program and selecting Check for Updates.

If they are both up to date, then as a last resort, try uninstalling the most recent update of MultiTerm here:

There was one occasion where the latest update of MultiTerm caused problems for some users.

Did you try all the options I suggested in the link I gave you in my first post?

Multiterm 2017 no longer working

The final one was that you can get free help from the Installation and Licensing Team by filling out the form here:

licensing and installation help

Fill out all the details then click 'Submit Case'. Most importantly, give them the email you are contactable on accurately and select 'Installation' under 'Case Type'...

All the best,

Ali

1. I have automatic updates turned on, so I'm on whatever is the most current

2. I have uninstalled and installed both Studio and MultiTerm multiple times since the problem occurred. Whatever is causing it, upgrades, reinstallations and even clean installs (I'm at least one PC on from the first occurrence) are not the solution.

3. I contacted support and they tried, well, lots of stuff including remote sessions. Last I heard from them was April 2018: "After reviewing all the aspects once again, and also discussed with 2nd level support, it is a defect of term recognition, that it seems to manifest in larger segments. I have logged it internally under CRQ-6274"

Since then, not a peep from anyone (I can't see the bug system and cases are automatically closed so I can't even get back to them without re-starting the whole rigmarole) and certainly no fix. Just me still tearing my hair out several years on over what should be a highly stable base functionality in a termbase tool.

1. I have automatic updates turned on, so I'm on whatever is the most current

2. I have uninstalled and installed both Studio and MultiTerm multiple times since the problem occurred. Whatever is causing it, upgrades, reinstallations and even clean installs (I'm at least one PC on from the first occurrence) are not the solution.

3. I contacted support and they tried, well, lots of stuff including remote sessions. Last I heard from them was April 2018: "After reviewing all the aspects once again, and also discussed with 2nd level support, it is a defect of term recognition, that it seems to manifest in larger segments. I have logged it internally under CRQ-6274"

Since then, not a peep from anyone (I can't see the bug system and cases are automatically closed so I can't even get back to them without re-starting the whole rigmarole) and certainly no fix. Just me still tearing my hair out several years on over what should be a highly stable base functionality in a termbase tool.

Hi Michael Bauer

If Support tried and failed, I'm sure they checked the termbase itself and also whether you have added MultiTerm and Studio to your virus checker's exceptions list.

Looks like you have done everything anyone has ever suggested to resolve your problem with MultiTerm. 

It might be worth contacting support again, though...

All the best,

Ali

That's easier said than done. When I tried the email, I got the "case closed, use https://gateway.sdl.com/" response. When I try that, I get a garbled page

from which I'm guessing that this feature is only open to someone with a support contract. But my view is that this is a base functionality which should get fixed irrespective of whether I have a support contract or not. If someone sells you a car with an engine that doesn't start, they can't fob you off just because you don't have a maintenance contract with them.

Michael Bauer

Michael Bauer said:

I have logged it internally under CRQ-6274"

I checked this, thank you for quoting the reference it makes it easier for me, and the issue has not been resolved as the dev team were unable to reproduce this after the 2015 CU10 and 2017 CU5 updates.

I have added a note that you are experiencing this in the latest version of Studio/MultiTerm and will let you know when I get some feedback on this.

Michael Bauer said:

When I try that, I get a garbled page

from which I'm guessing that this feature is only open to someone with a support contract.

That would be correct.  This doesn't mean you can't report an installation issue, it just means you don't have access to the support system in the same way as you would if you had a support contract.  Create a new case.

Michael Bauer

The dev team have also reproduced this issue and have scheduled some time to try and resolve this within the next update.

Thank you for chasing this up. I'll give it some more time then. I don't think I can face creating a new case at this stage and having the re-explain everything from scratch. It took me literally months to get someone to acknowledge that there was a problem and that I wasn't just imagining it.

So... a year on and I'm still having this problem. I really am not a happy bunny that over THREE years on and countless attempts at fixes and bug reports, such a basic functionality bug still hasn't been fixed. What happened to the "scheduled time"?