{"id":175187,"date":"2024-11-14T07:08:19","date_gmt":"2024-11-14T07:08:19","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=175187"},"modified":"2024-11-19T07:15:50","modified_gmt":"2024-11-19T07:15:50","slug":"fix-dag-member-server-not-operational-issue","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fix-dag-member-server-not-operational-issue\/","title":{"rendered":"How to Fix “DAG Member Server is not Operational” Issue?"},"content":{"rendered":"

In a Database Availability Group (DAG) setup with Exchange Server 2019, you may face a situation where one of the server nodes shows the status as ‘not operational.’ Although the issue is not that critical, you need to consider that in case of failure of other server\/s, the cluster will go down as the node (which is supposed to failover onto) is not operational. In addition, you need to also consider that the replication of data will not happen. In this case, if there is a failover, the data will be inconsistent. Below, we will be discussing the DAG member server<\/a> is not operational issue in detail and the possible solutions to fix the issue.<\/p>

What would happen if DAG Member Server is not Operational?<\/h2>

Since the Windows Cluster Service works in tandem with the Database Availability Group (DAG), you would also notice that the Cluster Service<\/strong> is not started although it is set to automatic. Though the cluster would still be operational as the Exchange Server is working on another node, you should consider the databases which are on the non-operational server. These databases will stop working. If the database copy is not healthy, it will not mount. You need to also consider, if the operational server fails, there will be no voting majority in the cluster since there are not enough nodes and the cluster will shutdown the services to protect the integrity.<\/p>

Ways to Fix the DAG Member Server is not Operational Issue<\/h2>

Here are some possible solutions to resolve the DAG Member Server is not Operational issue.<\/p>

1. Restart the DAG Member Server<\/strong><\/h3>

Sometimes, a simple reboot\/restart of the Exchange Server can resolve the issue of the member being shown as not operational. So, try to restart the affected server and see if the issue is resolved. You can also try to re-install the Failover Clustering feature in the affected server and restart the server.<\/p>

2. Check for any Changes<\/strong><\/h3>

It might happen that any changes that are done recently have caused the issue. You can consult with your IT administration team and network team to ensure that nothing has changed. You can also check the change management process of the company for any recorded changes. This will give an indication of where the problem might be and what might have caused it.<\/p>

3. Check and Start Windows Cluster Service<\/strong><\/h3>

The Database Availability Group depends on the Windows Server Cluster Service. Without this service, it will not be operational. The service is normally set to automatic startup. However, in this case, you will find that the service is not running. You can try to start the service.<\/p>

4. Check the Permissions<\/strong><\/h3>

When starting the Cluster Service, you may encounter an error saying, “Windows could not start the Cluster Service on Local Computer.” If you have setup the Cluster Service to run as a specific user, you should check the user for any issues, like the password has expired or the wrong password was configured or the account is locked out. You should also check the domain user (used to start the Cluster Service) has the necessary local administrator rights on the Exchange Server Machine. For this, go to Computer Management<\/strong> > Local Users<\/strong> and<\/strong> Groups<\/strong> > Groups<\/strong> and check if the user is part of the Administrators<\/strong> Group.<\/p>

\"check<\/figure>

You can also check the permissions of the user in the Failover Clustering Manager.<\/strong> For this,<\/p>