Exchange Database Stuck In Disconnected and Resynchronizing? Know How to Fix the Error

Summary: Is your Exchange database stuck, leaving your secondary server in limbo? You’re not alone. Whether it is due to a simple storage issue or a deeper corruption problem, we’ve got you covered. This write-up will provide complete information to solve the error “Exchange database stuck in disconnected and resynchronizing.” 

Microsoft Exchange Server plays a crucial role by enabling seamless communication and data management in an IT organization and other industry verticals around the globe. However, it is also evident that it is very prone to occasional corruption and other issues that can cause trouble for the Exchange database or other data in it.

The Exchange Server is set up by using DAG where the two servers join together and form one Exchange access server along with database copies with each other. Sometimes in the Database Availability Group, the Exchange user and IT administrator come across the error where the secondary EDB is disconnected and resynchronized. Then users face failure in the secondary Exchange database whereas the primary DB is in a healthy state/condition. Before proceeding to the solution, let’s look at the query given below that is commonly asked by users:

Table of Content

• Why Does the ‘Disconnected and Resynchronizing’ Error Occur?
• Manual Solutions to Fix the Error
  • 1. Check Storage On Secondary Server
  • 2. Check the Port Connection
  • 3. Reseed the Failed Database Copy
  • 4. Use the Exchange Admin Center
  • 5. Verify Active Directory (AD) Health
  • 6. Check Network Connectivity and Latency
  • 7. Restart the Microsoft Exchange Replication Service
• Most Reliable & Secure Approach
• Bringing It All Together

Why Does the ‘Disconnected and Resynchronizing’ Error Occur?

There could be many reasons behind this error. Here we have mentioned some of the possible causes behind this issue:

1. Database corruption
2. A problem occurred in the Active Directory
3. Space size issue in the secondary server
4. Blocked ports such as Transmission Control Protocol (TCP) / User Datagram Protocol (UDP)

Manual Solution to Fix the Error

There are a few manual walkarounds to fix

1. Check Storage On Secondary Server

The first and foremost thing is to check whether the storage on the secondary server is filled because the storage is the primary requirement for smoothing running of the Database Availability Group. Also, check the drive that stores the EDB and transaction log files, and see the storage space in the disk.

If it is filled, then remove unimportant data after when you dismount the database Exchange 2016, 2013, and 2010, and mount it back to see if the error is fixed/resolved.

2. Check the Port Connection

While performing other tasks or operations sometimes the network team is mistakenly blocked by them. Navigate to the Microsoft Exchange Server settings and see if the following ports which are given below are blocked or not. If it is blocked, then unblock it.

• – TCP Port 135 for “RPC”
• – TCP Port 64327 for “Log Shipping”
• – UDP Port 3343 for “Node Communication”

3. Reseed the Failed Database Copy

Users can use this solution when the secondary server database copy has failed. Here, the Exchange admin creates a fresh copy of the failed Exchange database by using the replica of another database.

Insert the following command given below to check the health of the Exchange database copes in the Database Availability Group.

Get-MailboxDatabaseCopyStatus

It shows the healthy, failed, or suspended and failed for Microsoft Exchange database copies. You can use the EAC and EMS to reseeding the failed database copy.

4. Use the Exchange Admin Center

Step 1. Login to EAC > Navigate to Servers > Databases.

Step 2. Choose the Exchange database to reseed. On the right side user will see the details such as DB name, content index state, etc… > Then, click on the update option

Step 3. Update the Exchange database copy page > Click on the browse button > Add the source server name > Select the save button

Step 4. Then the reseeding process will be started> Wait for time till the completion process is complete.

Step 5. Then check the state of the database and see if it changed

If users are defining the source server then insert the command given below to update the suspended database

When the server isn’t defined then insert the cmdlet to update the database

If you come across any error in the transaction in the log file then use the command given below:

Before starting the reseeding procedure it doesn’t delete the log file

This manual solution helps users to resolve the error “Exchange database stuck in disconnected and resynchronizing”. But if the cause behind this issue is corruption, we have to look for other options.

Most Reliable & Secure Approach

Recommended Solution: Use SysTools Exchange Server Recovery software to remove corruption from the offline / dismounted Microsoft Exchange database file and repair Exchange mailbox. This recovery manager for Exchange database tool provides Quick and Advance scan option that recover and repair EDB file which is severely damaged or corruption with no data loss.

Download Now Purchase Now

Moreover, this is an advanced recovery tool that easily recovers an unhealthy/damaged/corrupted Exchange database file without any data loss. It extracts mailboxes from EDB File Exchange 2016/2013 after recovery and exports them directly to the Live Exchange Server, Office 365, and HTML, PST, EML, MBOX, MSG, and PDF file formats in a simplified way.

5. Verify Active Directory (AD) Health

Another possible reason could be the issues in the Active Directory, it can also cause synchronization issues in the Database Availability Group (DAG).

Here are the steps to check the AD Health:

• Step 1. Use the following command to Check Replication to ensure all domain controllers are replicating correctly. 

repadmin /showrepl

• Step 2. Look for errors in the Directory Service log to check Event Viewer.
• Step 3. Use the following command to force synchronization between domain controllers to Synchronize AD.

repadmin /syncall

6. Check Network Connectivity and Latency 

Another potential reason could be the network issues between the primary and secondary servers can also result in improper synchronization.

Here are the steps to check the Network Connectivity and Latency:

• Step 1. You can use the Ping Test to check the connectivity between the servers. Run the below command: 

ping <SecondaryServerName>

• Step 2. Check the DAG network status and make sure it’s up and functional.
• Step 3. Another important factor to check is the Review of Event Logs. Check, if there are any network-related warnings or errors in the application and system logs. 

7. Restart the Microsoft Exchange Replication Service

Last but not least, restarting the service can resolve the issues of the Exchange Database being Stuck In Disconnected and Resynchronizing. Follow the below steps for the same:

• Step 1. On the secondary server, go to Services.
• Step 2. Navigate to Microsoft Exchange Replication Service.
• Step 3. Right-click and select Restart.

Bringing It All Together

Now users can fix the error ”Exchange database stuck in disconnected and resynchronizing” easily by using the manual solution provided in this write-up. If the problem occurred because of corruption then the user can use the recovery solution that resolves the database corruption Exchange 2010, 2013, 2016 efficiently without losing any data.