This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 98%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
i am facing MS Exchange Server 2019 CU9 crashed and reboot issue everytime than automatically add in cluster after few hours. There is no network issue. why find cluster errors and how to stopped rebooting and resolve this issue.
Facing following error in logs. please anyone suggest the solution.
My existing environment consist of three node.
Two Exchange Sever 2019 cu9 in Primary site with in same subnet
One is DR Exchange Server2019 cu9 in same Site but in different subnet
IPless DAG
Errors:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffffdb0e26307480, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 6d48016d-b6fb-47d5-aa87-3c9933356a20.
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
The Cluster Service service terminated unexpectedly. It has done this 10 time(s). The following corrective action will be taken in 7125000 milliseconds: Restart the service.
Based on your description, this question is related with Windows Cluster. I will help you add the tag (windows-server-clustering) to this thread.
I also find a related KB which may be useful to you: Responder ServiceHealthMSExchangeReplForceReboot causes Exchange Server to restart with Stop Error. I would suggest you check whether there exist related Event log on your server.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 79%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Once i experienced similar Blue Screen reboots on new Exchange server.
This was the reason (a very clever way, how microsoft resolves cluster service problem) - by rebooting whole server unexpectedly, it occurred every day, till i found this:
To update my story above; I've fixed this by now. The Get-HealthReport command showed me that the failover cluster part was failing. Although it was installed automatically by Exchange Setup the actual Failover Cluster service would not start. Now Exchange isn't exactly dependant of that so it does run, even the DAG, but still this was the reason why after that being down for 24 hours it triggered a reboot by triggering a BSOD. That's about the worst way to trigger a reboot in my opinion though.
Anyway, In my case I removed the failover cluster feature, rebooted, re-enabled failover cluster feature, rebooted and presto, everything green.