DTK Error: No Configuration Key or Text was entered to search for ... Search was term

Error: No Configuration Key or Text was entered to search for ... Search was terminated

Receive the above message at least when searching using: Search in Configuration Settings/Keys Phrase to search: (This will search configuration setting names and descriptions, and also configuration_keys if exact match)
And the search does not (no longer) matches a result.

Seems that the result should be different like no results returned rather than nothing entered for which to search.

How about a hint on what you searched for so we can perhaps try it too ... :lookaroun

Dim witted me. (Still trying to resolve a separate issue I'm having and came across this, sorry.)

PRODINFO_ATTRIBUTE_

This was attempted first while the key was present. When the screen refreshed, the search criteria was still present, there were results below, but the "message" above. Then once I deleted the keys that matched that search criteria, when I entered the criteria again, still go the same message from above.

Now, I was also trying to search on the following:
ATTRIBUTES_ENABLED
or
ATTRIBUTES_ENABLED_

and no results come back... But oddly those keys are associated with configuration->attributes... :/

When searching configuration keys note the instructions:

Phrase to search: (This will search configuration setting names and descriptions, and also configuration_keys if exact match)

Ajeh:

When searching configuration keys note the instructions:

Well see, that's where things seemed to go sideways... Before I deleted the original keys, searching on the part of the key returned the keys that matched/partially matched (associated with at least an older version of Dynamic Dropdowns), but the above search provided no result(s)...

Of course now that I have deleted it, I can't go back and validate without re-restoring this database... Also because of the problems I am experiencing I think I'd rather move on to a less ancient database... Now, that said, I probably need to 1) do an update on the database to utf8, and 2) try adding my own information one time to see if the problem goes away with fresh data...