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
Gastón Salomone
Hi, I cannot find any information on about this feature on hansamanual. That is the purpose, is it working, how it works or how must be configured to work ? For REST API many web request per...
23:47 3 Oct 2024
Paul Timms
Thanks Bror-Erik, it's hard to replicate so we won't know for sure until we upgrade the customer with this issue....
10:37 30 Sep 2024