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.
Reply
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
Re: CallHal(IsHansaWorldCustomer) in LOG
David Delač
Hi Piotr, The log entry:
2024-12-14 08:40:43 0.000 CallHal(IsHansaWorldCustomer) appears because the server is running with the verbosity=debug-detailed setting in its parameters.txt file. Thi...
09:43 16 Dec 2024
Re: The field Notes on Notes Tab in Contact register
Brittany McGrath
Hi Vaughn, I can confirm this has been fixed now and is live in Standard ERP 2024-11-20 Version: 85556786. Thank you. ...
10:04 10 Dec 2024