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
Gatis Jansons
Hi, Paul. Sounds like you're talking about REST API. And that your are overwriting data with older values if B managed to read record before A finished to update it. Classic conflict resolution ...
14:53 19 Mar 2026
Carolina Valentino
hello Andis.. yes the Time out is for all users, I completely understand the point and we can propose it as a wish...
14:35 19 Mar 2026