Stéphane Clément 

Is this the only termbase that has proven problematic?
Is it a certain term you are struggling with or is it the search feature in general?

Because I cant help but to wonder how you can validate the Term does exist - if you cant search for it

Stéphane Clément said:

- The term I was looking for existed in both languages in the entrie

Regardless, do you happen to know the Entry ID and can you use that to troubleshoot this further?

What type of search are you using? Perhaps play around to see if it find what you are looking for

What is your display Layout?
Try the old MultiTerm Classic or Source/Target as a means to troubleshoot this further.

Is your MultiTerm up to date (via Help - Check for Updates) and have you tried to Reorganise your Termase (Termbase Management)

Looking forward to your findings 

Lyds

I have the same problem. I thought it was an update error but I just upgraded Multiterm to 2022 SR2 - 17.2.3.2795 and the error persists.

I can verify that the term exists in the database because I can use the scrollbar to scroll down to whatever term (or part thereof) I'm searching for but neither hitting Enter no the Search icon is working as it used to.

Switching to Classic Layout makes no change.

Go To Entry Number is greyed out.

I've tried reorganizing the termbase, no change. There's something broken here.

ADDENDUM: because I had to really check a term, I thought I'd add the term again and use the Merge option to call up the entry. Multiterm then tells me the term exists, but when I tell it to Merge, it throws this error:

Lydia Simplicio 

Hi Michael, 

I have exactly the same problem as you. Did you manage to solve it ?

Thanks a lot,

Lydia Simplicio Michael Bauer 

No, it's still broken. The weird thing is, I run exactly the same setup on two Win 10 desktop machines (not the same make), one has this issue, the other doesn't. I'm just hoping RWS won't spread the error round to my main machine...

No, it's still broken. The weird thing is, I run exactly the same setup on two Win 10 desktop machines (not the same make), one has this issue, the other doesn't. I'm just hoping RWS won't spread the error round to my main machine...

Hi Michael,

You can try this thread. It worked for me. 

That worked for me, thanks!