Re: Strange communication error never seen
Paul Timms
10-22-18
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.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Bror-Erik Kotiranta
Hello, these spikes in cpu usage i do believe have been fixed in the 8.5 2026 08 29 version, can you please have a try there?...
13:30 10 Sep 2026
Bror-Erik Kotiranta
Hello, I did not see this as a problem in the newer versions. Have you had a chance to visit the new version and test it out ?...
13:29 10 Sep 2026