This can also happen if the HANSA.HDB is renamed, and the service is started back up. It creates an "empty" HANSA.HDB which is not set up for remote access, and the client gets that message.
I've found an issue which I'm trying to find the best way to resolve.
An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named.
If timeout minutes are specified in Optional Features, then all idle users are...
