SERP client renames HANSA.HDB itself
Aldevinas Katkus
5-5-17
We had a call from customer where CN stopped the server and users were unable to login. On one PC the client's HANSA.HDB became HANSA.HDBold and the user could not connect to the server after we started the server. Why it happened only on one client? When (under what circumstances) could this happen?
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
qupdating collisions
Paul Timms
I've found an issue which I'm trying to find the best way to resolve. An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
17:59 20 Feb 2026
Optional Features > Idle Client Timeout
Andis Blicāns, Grasko
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named. If timeout minutes are specified in Optional Features, then all idle users are...
15:53 18 Feb 2026