I have a Domino server running on Windows server 2019 standard. Windows crashes on rare occasion (maybe every few months). When it does, the Domino service does not restart.
Searching the event viewer, I can't tell what caused the OS to crash
I can't tell why Domino doesn't restart after the server reboots even though it is set to startup automatically.
For your awareness, we have launched a new Digital Solutions Community site (https://developer.ds.hcl-software.com/), which includes our new product forums. The content for our legacy product forums will soon be migrated to this new site. If you haven’t yet done so, we encourage you to sign up on the site and engage with the community of experts for our products!
Regarding the question raised in this forum:
Have you tried starting Domino Service on a Regular Windows condition?
Does it start?
Can you please also check the console.log if there is any hint why the Domino Server did not start automatically?
It seems the issue is the OS and not domino. There arent going to be any domino crash logs as it would most likely not crash. The OS just shuts down.
Better to address the OS crash issue.
It would be pertinent to check as to what happens, if you restart the OS after it has auto restarted or manually restarted after the crash. Does domino restart automatically in this case.
Also check if the domino server process does not start at all after a crash. Or the domino process starts and goes into crash recovery processes or goes into crash recovery process and hangs there.
Checking the status of domino server processes after reboot post OS crash via task manager may provide a clue.
We understand that During the Windows OS crash, the Domino service failed to start after OS reboot.
Please check if the HCL Domino service is set with "Automatic" option.
We have seen few issues where the HCL Domino service failed to start after an OS reboot.
One of the possible reasons we noticed from the OS end is due to a NIC teaming issue in Windows Server. We have found the following published information on the Microsoft site about the NIC teaming issue on Windows Server 2016.
Title: Services do not automatically start after reboot of a computer that uses NIC teaming
We suspect similar issue might have happened in your environment. Solution: To resolve this issue caused from OS end, please set the HCL Domino servicer service start-up type as “Automatic (Delayed Start)”.
By Setting the Domino service to “Automatic (Delayed Start)”, after the OS startup is completed, the Domino service startup will be initiated.
We hope the above information will help in answering your concerns.
We understand that During the Windows OS crash, the Domino service failed to start after OS reboot.
Please check if the HCL Domino service is set with “Automatic” option.
We have seen few issues where the HCL Domino service failed to start after an OS reboot.
One of the possible reasons we noticed from the OS end is due to a NIC teaming issue in Windows Server.
We have found the following published information on the Microsoft site about the NIC teaming issue on Windows Server 2016.
Title: Services do not automatically start after reboot of a computer that uses NIC teaming
We suspect similar issue might have happened in your environment.
Solution:
To resolve this issue caused from OS end, please set the HCL Domino servicer service start-up type as “Automatic (Delayed Start)”.
By Setting the Domino service to “Automatic (Delayed Start)”, after the OS startup is completed, the Domino service startup will be initiated.
We hope the above information will help in answering your concerns.
Thank you for all the responses. I really can’t resolve the Domino startup issue until we address whatever is causing the OS crashes, so I’m focused on that.
It is possible that a windows update might have caused this (since you’ve noticed that it crashes once every few months). Windows update may cause the Domino to crash since most of the windows updates are all about services.