Cloud Node with D4 errors in log
Sanjay Parbhoo
11-22-18
We have a cloud node instance where the service cannot start and there is a d4 error message in the log file. This suggests that the database has been damaged and needs to be recreated.

What is the procedure to resolve this?
Håvar Falck-Andersen
11-23-18
I have the same problem on a client (windows). How to restore the cloud node HDB ?
David Delač
11-23-18
Hello Sanjay,
Thank you for your enquiry. Have you tried exporting and importing back the same database? This usually works and in case it doesn't then I would suggest you to try importing latest backup.

Best Regards,
David D.
HansaWorld Sweden
Tomas J.
3-28-19
If a CN database is damaged, then an export/import can be done (only for advanced users who can recognize such issue)

Stop CN service

Go to CN directory and perform normal export/import
Start CN service



Manual steps to recover if D4 and backup can not be created

hansa-cloudnode --rawdata
ren HANSA.HDB HANSA.HDB.D4
hansa-cloudnode rawdata.txt
hansa-cloudnode --backup
ren HANSA.HDB HANSA.HDB.BAK
hansa-cloudnode Backup\TB.TXT
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
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
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