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
Paul Timms
I would like to know what BackgroundHALShouldPause does, and how to use it. While it's listed in the HAL Primitives report, it is not used in source code and it doesn't appear in the LMS HAL...
18:15 30 Jan 2026
Bror-Erik Kotiranta
Please create a bugreport on the problems...
10:38 26 Jan 2026