{"id":126805,"date":"2023-03-14T06:58:45","date_gmt":"2023-03-14T06:58:45","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=126805"},"modified":"2024-06-12T09:42:11","modified_gmt":"2024-06-12T09:42:11","slug":"exchange-dag-cluster-service-terminated-with-error-7024","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/exchange-dag-cluster-service-terminated-with-error-7024\/","title":{"rendered":"Exchange DAG Cluster Service Terminated with Error 7024"},"content":{"rendered":"

In Exchange Server with high availability setup, you may encounter an error – Exchange DAG service terminated with error code 7024<\/strong>. This may stop the users from accessing their data. When you investigate the issue, you might find out that the databases in Exchange Server are not mounted<\/a><\/strong>. In such a case, you will start mounting the databases, but the databases may fail to mount, even the public folder databases. In the services<\/strong> management console, you will see that the Cluster<\/strong> Service<\/strong> is also stopped. Any attempts to start the service will be useless. In the Event<\/strong> Viewer<\/strong>, under the System<\/strong> log, you will notice a similar error as given below.<\/p>

Log Name: System
Source: Service Control Manager
Date: 1\/1\/2023 12:07:44 AM
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N\/A
Computer: EX01.mycompany.lan
Description: The Cluster Service service terminated with service-specific error Log service encountered an invalid log block..<\/code><\/p>

The error message doesn’t say much. However, when you dig deeper in the log, you might see a critical error on the Quorum Manager<\/strong>.<\/p>

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 1\/1\/2023 12:00:43 AM
Event ID: 1177
Task Category: Quorum Manager
Level: Critical
Keywords:
User: SYSTEM
Computer: EX01.mycompany.lan
Description: The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.<\/code><\/p>

In addition, you might find other messages, such as:<\/p>

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 1\/1\/2023 12:00:43 AM
Event ID: 1135
Task Category: Node Mgr
Level: Critical
Keywords:    
User: SYSTEM
Computer: EX02.mycompany.lan
Description: Cluster node 'EX02' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.<\/code><\/p>

The above messages indicate that the cluster has failed and both DAG members in the clusters went offline. You can also see that the reason for the failure could be a network issue between the servers.<\/p>

Solutions to Resolve the Exchange DAG Service Terminated Error<\/h2>

You need to keep in mind that if half plus one nodes fail, the cluster will automatically go in shutdown state to prevent any corruption. This is by design to protect the integrity of the servers and data.<\/p>

Apart from trying to restore the services, there are a few troubleshooting procedures that you can perform.<\/p>

The error message indicates issues with network. Therefore, you need to make sure that there weren’t any disconnections on the server or any configuration issue on the VLAN or other network devices, which could have hindered the connectivity between the two servers over the network or the heartbeat network.<\/p>

It is important to keep a change management log of all the changes as you can always trace back to see what changed from when the servers were working to when they failed.<\/p>

Another thing to check is the cluster database BLF file. This file contains the metadata of the cluster, which is used to manage access to the log data. It might happen that the CLUSDB.BLF<\/strong> file is corrupted. In this case, you can do the following:<\/p>